Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8206e75235b1ed2fc27daef92ad21d9dc88f07707d04a141908a6f3028e408a

Tx prefix hash: d564ceb3b5b97c7b9e05257e5d5290618bc318477a0b98d5aaf4a586dedeabe5
Tx public key: c9c6f2f811ef6af757293c8293ef048d510cf60d799cfa6e2b521238fba84ee1
Timestamp: 1732124410 Timestamp [UCT]: 2024-11-20 17:40:10 Age [y:d:h:m:s]: 00:148:21:51:38
Block: 1157977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106258 RingCT/type: yes/0
Extra: 01c9c6f2f811ef6af757293c8293ef048d510cf60d799cfa6e2b521238fba84ee1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbea62837d66605cd89f04331a7e285cd743641c5477001ced250a0edf5d9d2c 0.600000000000 1643600 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": 1157987, "vin": [ { "gen": { "height": 1157977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbea62837d66605cd89f04331a7e285cd743641c5477001ced250a0edf5d9d2c" } } ], "extra": [ 1, 201, 198, 242, 248, 17, 239, 106, 247, 87, 41, 60, 130, 147, 239, 4, 141, 81, 12, 246, 13, 121, 156, 250, 110, 43, 82, 18, 56, 251, 168, 78, 225, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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