Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c4daf17503320ecb05c15d4935ba04649e53bdfb6c0506ec8e7c12c573aec83

Tx prefix hash: 0c17dcf9a1c5a443bdc8d9f5f1c9ffed181f4a2d3559c327b9aeaa50e7d575c9
Tx public key: 711fb3fc1f28676488ed840cff4d7b6b8d7612cb782164e4dc742cf8df97b5d4
Timestamp: 1750019042 Timestamp [UCT]: 2025-06-15 20:24:02 Age [y:d:h:m:s]: 00:156:02:47:32
Block: 1305771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109352 RingCT/type: yes/0
Extra: 01711fb3fc1f28676488ed840cff4d7b6b8d7612cb782164e4dc742cf8df97b5d4021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f352ba116d3ecd6d557330af0a498196a040b58c3e71d0ad26ee9ef893f88662 0.600000000000 1793372 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": 1305781, "vin": [ { "gen": { "height": 1305771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f352ba116d3ecd6d557330af0a498196a040b58c3e71d0ad26ee9ef893f88662" } } ], "extra": [ 1, 113, 31, 179, 252, 31, 40, 103, 100, 136, 237, 132, 12, 255, 77, 123, 107, 141, 118, 18, 203, 120, 33, 100, 228, 220, 116, 44, 248, 223, 151, 181, 212, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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