Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf624444016c0ed0e384a68fffd15cf97a28ff778a3d4f0040272a27900a2d5e

Tx prefix hash: 758aa938ea181b5a6ccf06577175b1941eb171278f1c209bd3eb6d3cda07414c
Tx public key: 1810d11fbf72a6781b31c13b5aea3c274e57f2e385b903464d67ab8da68dfdd3
Timestamp: 1765400245 Timestamp [UCT]: 2025-12-10 20:57:25 Age [y:d:h:m:s]: 00:050:09:20:37
Block: 1430811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35908 RingCT/type: yes/0
Extra: 011810d11fbf72a6781b31c13b5aea3c274e57f2e385b903464d67ab8da68dfdd3021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d494db2e208574ce5370abfb20bb5d3cb7092c88710c03e51406e742c445e98 0.600000000000 1919564 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": 1430821, "vin": [ { "gen": { "height": 1430811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d494db2e208574ce5370abfb20bb5d3cb7092c88710c03e51406e742c445e98" } } ], "extra": [ 1, 24, 16, 209, 31, 191, 114, 166, 120, 27, 49, 193, 59, 90, 234, 60, 39, 78, 87, 242, 227, 133, 185, 3, 70, 77, 103, 171, 141, 166, 141, 253, 211, 2, 17, 0, 0, 0, 3, 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