Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12cc067b70657b43c6ee0205ddce498cf82f29778fad8b81dd48950c6a175a38

Tx prefix hash: a0b6f0bf19f0154f796faff8d0114aeb2b340b781db0a598615adc9a5d27aa25
Tx public key: f8ea0bc94899cda23d918096665ace0765d3a3c4fce9923fc9f4ac29d43ad35f
Timestamp: 1749692711 Timestamp [UCT]: 2025-06-12 01:45:11 Age [y:d:h:m:s]: 00:151:19:49:11
Block: 1303137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106214 RingCT/type: yes/0
Extra: 01f8ea0bc94899cda23d918096665ace0765d3a3c4fce9923fc9f4ac29d43ad35f02110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05cd16a7e570c1db2ff6415d40ae8fa6f55ddf3e1bd876d7f78fa68079b0e4f7 0.600000000000 1790712 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": 1303147, "vin": [ { "gen": { "height": 1303137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05cd16a7e570c1db2ff6415d40ae8fa6f55ddf3e1bd876d7f78fa68079b0e4f7" } } ], "extra": [ 1, 248, 234, 11, 201, 72, 153, 205, 162, 61, 145, 128, 150, 102, 90, 206, 7, 101, 211, 163, 196, 252, 233, 146, 63, 201, 244, 172, 41, 212, 58, 211, 95, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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