Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e6ff06fa805f6b1d6678ffaad2c227a446abc3f743bb4ad67df9d27c063c61b

Tx prefix hash: b319457b98ef107d022281e7f06ab956af9a9ab6386c8512c41961968a5b6ead
Tx public key: cce8919f712e4debbf34c7c5ac3557fc58260820eba56b0c6cca74a4b5dfdc7c
Timestamp: 1703562460 Timestamp [UCT]: 2023-12-26 03:47:40 Age [y:d:h:m:s]: 01:126:17:49:26
Block: 921280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351710 RingCT/type: yes/0
Extra: 01cce8919f712e4debbf34c7c5ac3557fc58260820eba56b0c6cca74a4b5dfdc7c021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f179b25fa75cdc793c5655af5f678113b0f5c542e169a1872b165a50aef0d462 0.600000000000 1378966 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": 921290, "vin": [ { "gen": { "height": 921280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f179b25fa75cdc793c5655af5f678113b0f5c542e169a1872b165a50aef0d462" } } ], "extra": [ 1, 204, 232, 145, 159, 113, 46, 77, 235, 191, 52, 199, 197, 172, 53, 87, 252, 88, 38, 8, 32, 235, 165, 107, 12, 108, 202, 116, 164, 181, 223, 220, 124, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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