Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e605d65b4a5274a940e42516cd350b8e814ac473ce43dcaf934a1d0af1ef710a

Tx prefix hash: 51bec3a36ff2b0f41809ba4011d2d2610e592f88bd372dbd384229b1efc2e99d
Tx public key: 2166d6c826cc2151dea5aea31ec5f9b140228bd36f24820ff807fa2d990e9a43
Timestamp: 1736079881 Timestamp [UCT]: 2025-01-05 12:24:41 Age [y:d:h:m:s]: 00:100:22:44:57
Block: 1190742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71929 RingCT/type: yes/0
Extra: 012166d6c826cc2151dea5aea31ec5f9b140228bd36f24820ff807fa2d990e9a43021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c768005c9d168484af7712c59e2801e5a36b6a0fd7011cd7ec0a81200d723e8 0.600000000000 1677261 of 15

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": 1190752, "vin": [ { "gen": { "height": 1190742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c768005c9d168484af7712c59e2801e5a36b6a0fd7011cd7ec0a81200d723e8" } } ], "extra": [ 1, 33, 102, 214, 200, 38, 204, 33, 81, 222, 165, 174, 163, 30, 197, 249, 177, 64, 34, 139, 211, 111, 36, 130, 15, 248, 7, 250, 45, 153, 14, 154, 67, 2, 17, 0, 0, 0, 4, 0, 127, 151, 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