Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8efc98497f392aebe0f196ead8e2a5651e3e0384c870f2c6243c76e9d31cd537

Tx prefix hash: cc2e6cd82bef29afd20a9b14d35af2c9fca19126aca058fa10481499cb568e33
Tx public key: 6fa6ec99647410aa1a2fcedab0fac0259b3e54d0e4436f2bcfbe33dc075c01b7
Timestamp: 1765551410 Timestamp [UCT]: 2025-12-12 14:56:50 Age [y:d:h:m:s]: 00:010:20:40:44
Block: 1432065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7767 RingCT/type: yes/0
Extra: 016fa6ec99647410aa1a2fcedab0fac0259b3e54d0e4436f2bcfbe33dc075c01b7021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abebae35a20eaf16f398533108404168a3d1b98e5b1737147613e3ea0d93d1c4 0.600000000000 1920844 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": 1432075, "vin": [ { "gen": { "height": 1432065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abebae35a20eaf16f398533108404168a3d1b98e5b1737147613e3ea0d93d1c4" } } ], "extra": [ 1, 111, 166, 236, 153, 100, 116, 16, 170, 26, 47, 206, 218, 176, 250, 192, 37, 155, 62, 84, 208, 228, 67, 111, 43, 207, 190, 51, 220, 7, 92, 1, 183, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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