Transaction | Node.js bindings for DAML

Filtered view of an on-ledger transaction.

Example:

{
    commandId: 'some-command-id',
    effectiveAt: {
        seconds: 1554382900
        nanoseconds: 0
    },
    events: [
        {
            eventType: 'created',
            eventId: 'some-event-id',
            contractId: 'some-contract-id',
            templateId: {
                packageId: 'my-package-id',
                moduleName: 'SomeModule',
                entityName: 'SomeTemplate'
            },
            arguments: {
                fields: {
                    someKey: { valueType: 'bool', bool: true }
                }
            },
            witnessParties: [ 'Alice', 'Bob' ]
        }
    ],
    offset: '42',
    transactionId: 'some-tx-id',
    workflowId: 'some-workflow-id'
}

To express values in a more concise way, you can have a look at the ValueHelpers.

see: Timestamp
see: Event
see: Identifier
see: Record

Hierarchy

Transaction

Index

Properties

Optional commandId

commandId: undefined | string

The identifier of the command which resulted in this transaction.

Missing for everyone except the submitting party.

effectiveAt

effectiveAt: Timestamp

Ledger effective time.

events

events: Event[]

The collection of events.

offset

offset: string

The absolute offset.

transactionId

transactionId: string

Assigned by the server. Useful for correlating logs.

Optional workflowId

workflowId: undefined | string

The workflow identifier used in command submission.