Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 55a9efdf2c46a8d794359dfbbc11acbbbdfd82ed2d6890961a84ca660ce8662a

Tx prefix hash: 421e58bc518ebe84422c75cb36af620739621ad2d4cc184a87163536a803ab21
Tx public key: 73b2a1d24adc919a39c7868123ac0c13b70c518601c914dbc9ced3fc0efe3435
Timestamp: 1699378500 Timestamp [UCT]: 2023-11-07 17:35:00 Age [y:d:h:m:s]: 01:114:10:15:43
Block: 886600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342936 RingCT/type: yes/0
Extra: 0173b2a1d24adc919a39c7868123ac0c13b70c518601c914dbc9ced3fc0efe343502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.708477656000 dcy

stealth address amount amount idx
00: e59ab3774ee0e8e43b6140be77ca90dce50777cae8bde048288c0ff2c0f3b0a8 0.708477656000 1342427 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 886610, "vin": [ { "gen": { "height": 886600 } } ], "vout": [ { "amount": 708477656, "target": { "key": "e59ab3774ee0e8e43b6140be77ca90dce50777cae8bde048288c0ff2c0f3b0a8" } } ], "extra": [ 1, 115, 178, 161, 210, 74, 220, 145, 154, 57, 199, 134, 129, 35, 172, 12, 19, 183, 12, 81, 134, 1, 201, 20, 219, 201, 206, 211, 252, 14, 254, 52, 53, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8