Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56fab7577e6ad0e3fd2aca7de7196557af858bd9b045b85a8f0c518b52b6bb01

Tx prefix hash: e4ae5cf65ed41b8a1a111b505b018b73cac6f47f73367ade558ff9f73ca878fe
Tx public key: 16492800cb99b7c12c402dfaaa291635e551dbc75a5914b11f7bc9a254e8ae87
Timestamp: 1708532096 Timestamp [UCT]: 2024-02-21 16:14:56 Age [y:d:h:m:s]: 01:042:21:33:00
Block: 962484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291676 RingCT/type: yes/0
Extra: 0116492800cb99b7c12c402dfaaa291635e551dbc75a5914b11f7bc9a254e8ae870211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9b6c81df3096b7f0bd2e38bb56cd4148cc7aaf5512a62bd47f35cb8aadcabf6 0.600000000000 1422121 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": 962494, "vin": [ { "gen": { "height": 962484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9b6c81df3096b7f0bd2e38bb56cd4148cc7aaf5512a62bd47f35cb8aadcabf6" } } ], "extra": [ 1, 22, 73, 40, 0, 203, 153, 183, 193, 44, 64, 45, 250, 170, 41, 22, 53, 229, 81, 219, 199, 90, 89, 20, 177, 31, 123, 201, 162, 84, 232, 174, 135, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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