Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66a54470cccc7ae2bfce6bd115544ea64ac2ad7f4ded8ac44a1bce1af4990a90

Tx prefix hash: 037a30202a440ebb0b41f24c4b782cb5b42eaf3b43e9e6f52e2ba4559b5c7bd4
Tx public key: 64f8f72f314a0f6f73df93184f3a7dec01c74876e5f825b7515d1c89c8f91bfd
Timestamp: 1760944084 Timestamp [UCT]: 2025-10-20 07:08:04 Age [y:d:h:m:s]: 00:064:05:41:53
Block: 1393901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45967 RingCT/type: yes/0
Extra: 0164f8f72f314a0f6f73df93184f3a7dec01c74876e5f825b7515d1c89c8f91bfd02110000000adf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e3b1b452d940d3a8a47f00666b74da4c1b9c3a89ecd32177d9d3c73766a755 0.600000000000 1882168 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": 1393911, "vin": [ { "gen": { "height": 1393901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e3b1b452d940d3a8a47f00666b74da4c1b9c3a89ecd32177d9d3c73766a755" } } ], "extra": [ 1, 100, 248, 247, 47, 49, 74, 15, 111, 115, 223, 147, 24, 79, 58, 125, 236, 1, 199, 72, 118, 229, 248, 37, 183, 81, 93, 28, 137, 200, 249, 27, 253, 2, 17, 0, 0, 0, 10, 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