Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ef48ddc21b59ddf28b2dd64961d7bf7e7d14f5ebd2fdf26cac7d2449f383831

Tx prefix hash: 5d80eea890f4277a031d77e18c2d77f32caa9b2ba2779f2459fe388363a916e6
Tx public key: 89b4f2e8245cfcbbe8f8dcdc520698506a9cc8f2c7c016952b16cbde47a03ac9
Timestamp: 1762388787 Timestamp [UCT]: 2025-11-06 00:26:27 Age [y:d:h:m:s]: 00:056:21:40:37
Block: 1405845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40756 RingCT/type: yes/0
Extra: 0189b4f2e8245cfcbbe8f8dcdc520698506a9cc8f2c7c016952b16cbde47a03ac902110000000cdf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 196f981787ea308721cac25e846a4818ee6d2537036af64ae9902cca4c74599c 0.600000000000 1894226 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": 1405855, "vin": [ { "gen": { "height": 1405845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "196f981787ea308721cac25e846a4818ee6d2537036af64ae9902cca4c74599c" } } ], "extra": [ 1, 137, 180, 242, 232, 36, 92, 252, 187, 232, 248, 220, 220, 82, 6, 152, 80, 106, 156, 200, 242, 199, 192, 22, 149, 43, 22, 203, 222, 71, 160, 58, 201, 2, 17, 0, 0, 0, 12, 223, 90, 36, 122, 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