Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecf545ee683441b672b7340dac9ee7ea44252bc03ccd9a36f6be33fc2434631e

Tx prefix hash: 57f14cd948e1756cd384c1385bb994732e845c3b2bc3524b7c5f9e805b3c1a8a
Tx public key: 5c4defafbe6ab1120f4c58e1e312ca265719fde29750c9b104ba0bf43179e839
Timestamp: 1593017317 Timestamp [UCT]: 2020-06-24 16:48:37 Age [y:d:h:m:s]: 04:190:03:22:31
Block: 110406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076261 RingCT/type: yes/0
Extra: 015c4defafbe6ab1120f4c58e1e312ca265719fde29750c9b104ba0bf43179e83902110000000246a11e8a000000000000000000

1 output(s) for total of 264.350318341000 dcy

stealth address amount amount idx
00: b7ed1b60ceb55e1419a00770a1ffa2a90b611e1afb4ed4c0482f15450b98236d 264.350318341000 191288 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": 110416, "vin": [ { "gen": { "height": 110406 } } ], "vout": [ { "amount": 264350318341, "target": { "key": "b7ed1b60ceb55e1419a00770a1ffa2a90b611e1afb4ed4c0482f15450b98236d" } } ], "extra": [ 1, 92, 77, 239, 175, 190, 106, 177, 18, 15, 76, 88, 225, 227, 18, 202, 38, 87, 25, 253, 226, 151, 80, 201, 177, 4, 186, 11, 244, 49, 121, 232, 57, 2, 17, 0, 0, 0, 2, 70, 161, 30, 138, 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