Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 466512ac844c198d36bd566c3c67497d0eaefae05cb2b31d3551f0b91fef58bc

Tx prefix hash: e477c8183a85a730c0d634f816266bc76a90ee0d8957821db2e759e10096162d
Tx public key: 0eba6404fb338acfe30aa6b75dabe7cb78cdabdee19f35b2a9512588ab2c29f6
Timestamp: 1764121860 Timestamp [UCT]: 2025-11-26 01:51:00 Age [y:d:h:m:s]: 00:001:07:03:24
Block: 1420218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933 RingCT/type: yes/0
Extra: 010eba6404fb338acfe30aa6b75dabe7cb78cdabdee19f35b2a9512588ab2c29f60211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3edeb4fa0a9cc21e0202954c3edfbaabb6704f9c1f64f78720bc8df14c2e523d 0.600000000000 1908759 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": 1420228, "vin": [ { "gen": { "height": 1420218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3edeb4fa0a9cc21e0202954c3edfbaabb6704f9c1f64f78720bc8df14c2e523d" } } ], "extra": [ 1, 14, 186, 100, 4, 251, 51, 138, 207, 227, 10, 166, 183, 93, 171, 231, 203, 120, 205, 171, 222, 225, 159, 53, 178, 169, 81, 37, 136, 171, 44, 41, 246, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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