Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0a093fcc21ea1c3fd1eccdc18e230aaf16c4673da558185a89fc721a5914886

Tx prefix hash: 21d070331497fba6253553cbd400b8ef225704ddd911859c4d8708e8429cf2ef
Tx public key: 4f29638ffdbb302b5cf4c3930a26f876d2d442b475693783913d519d8d3b4f54
Timestamp: 1744742953 Timestamp [UCT]: 2025-04-15 18:49:13 Age [y:d:h:m:s]: 00:215:18:26:26
Block: 1262180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151934 RingCT/type: yes/0
Extra: 014f29638ffdbb302b5cf4c3930a26f876d2d442b475693783913d519d8d3b4f540211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff6c292c67f8024b90a1fb83d703e902eb01adf8ecfe5a25946a661e119e9ab8 0.600000000000 1749357 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": 1262190, "vin": [ { "gen": { "height": 1262180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff6c292c67f8024b90a1fb83d703e902eb01adf8ecfe5a25946a661e119e9ab8" } } ], "extra": [ 1, 79, 41, 99, 143, 253, 187, 48, 43, 92, 244, 195, 147, 10, 38, 248, 118, 210, 212, 66, 180, 117, 105, 55, 131, 145, 61, 81, 157, 141, 59, 79, 84, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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