Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15b14374f953817ecfa6721324a3a1a910933766a3e2ed3c7d6500cf1f5d16b0

Tx prefix hash: 53702010d43c4c782dee71467e17c26743e2d19b5b4585e675dcc730af1f1bf3
Tx public key: ad9adf639559da30bb961c1a3ff8f04e51b52acead55f46d08e7459683f3a9be
Timestamp: 1727269106 Timestamp [UCT]: 2024-09-25 12:58:26 Age [y:d:h:m:s]: 00:107:17:44:31
Block: 1117823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77036 RingCT/type: yes/0
Extra: 01ad9adf639559da30bb961c1a3ff8f04e51b52acead55f46d08e7459683f3a9be02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b49964f153f8fb2235cba0c876e917894482be9be40d5455d8236750d84e9e8 0.600000000000 1598798 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": 1117833, "vin": [ { "gen": { "height": 1117823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b49964f153f8fb2235cba0c876e917894482be9be40d5455d8236750d84e9e8" } } ], "extra": [ 1, 173, 154, 223, 99, 149, 89, 218, 48, 187, 150, 28, 26, 63, 248, 240, 78, 81, 181, 42, 206, 173, 85, 244, 109, 8, 231, 69, 150, 131, 243, 169, 190, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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