Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e41e907d8303998d3eb7fe161113b0de782bc70208a033746c8f934468bcb5c2

Tx prefix hash: aa1f40f595c6bb6c9cb937c2362af23c857ad22f83526c59a82939ac6170edd3
Tx public key: 0a01f3f60a5740170b9ab05b1e288c4a6ef71a377cc263e1bfe5d94406e454d3
Timestamp: 1711568075 Timestamp [UCT]: 2024-03-27 19:34:35 Age [y:d:h:m:s]: 01:010:23:38:15
Block: 987669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268790 RingCT/type: yes/0
Extra: 010a01f3f60a5740170b9ab05b1e288c4a6ef71a377cc263e1bfe5d94406e454d30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a9f3edec41dec71bb16a6f7d983e47e0bcf9af0737ec6768efffc29d81d2f50 0.600000000000 1447924 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": 987679, "vin": [ { "gen": { "height": 987669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a9f3edec41dec71bb16a6f7d983e47e0bcf9af0737ec6768efffc29d81d2f50" } } ], "extra": [ 1, 10, 1, 243, 246, 10, 87, 64, 23, 11, 154, 176, 91, 30, 40, 140, 74, 110, 247, 26, 55, 124, 194, 99, 225, 191, 229, 217, 68, 6, 228, 84, 211, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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