Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ebd82d31518d91daa86c0b68ce3efcb4b31b5cd0716072a998bfff215235393

Tx prefix hash: d571c9a272a1f91c38952e2fadcdb3c821870b22bfff9ce3ca063c91fba3a21e
Tx public key: 8928037f38a149a5335f5f877f35884c45e797d564a16d50ab9aa1155d5b30a4
Timestamp: 1751948905 Timestamp [UCT]: 2025-07-08 04:28:25 Age [y:d:h:m:s]: 00:136:12:51:21
Block: 1321072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96018 RingCT/type: yes/0
Extra: 018928037f38a149a5335f5f877f35884c45e797d564a16d50ab9aa1155d5b30a4021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12d4bd0df2640bdfd8b0f8a4e5f8ce3f82b69f7fc2089be395d0b3b53392778a 0.600000000000 1808775 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": 1321082, "vin": [ { "gen": { "height": 1321072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12d4bd0df2640bdfd8b0f8a4e5f8ce3f82b69f7fc2089be395d0b3b53392778a" } } ], "extra": [ 1, 137, 40, 3, 127, 56, 161, 73, 165, 51, 95, 95, 135, 127, 53, 136, 76, 69, 231, 151, 213, 100, 161, 109, 80, 171, 154, 161, 21, 93, 91, 48, 164, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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