Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8666b42f2808cf47d8fdf5acefb8e97df9cd1ffa67ea7d4d954fa94677aca6e3

Tx prefix hash: 572608fed6e44be8e9e9c1af24c3faa56df4e6c4516a6c82ea63b8e02718c19a
Tx public key: 8d8462c4c08625c71320238bd76b3510180a52d6ea1e736175668317815def3e
Timestamp: 1715873637 Timestamp [UCT]: 2024-05-16 15:33:57 Age [y:d:h:m:s]: 00:331:17:50:13
Block: 1023345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237125 RingCT/type: yes/0
Extra: 018d8462c4c08625c71320238bd76b3510180a52d6ea1e736175668317815def3e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a434ee6d4e8051a2be2761d6e21d296d051653609f40879328957c213a3aa5 0.600000000000 1488258 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": 1023355, "vin": [ { "gen": { "height": 1023345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a434ee6d4e8051a2be2761d6e21d296d051653609f40879328957c213a3aa5" } } ], "extra": [ 1, 141, 132, 98, 196, 192, 134, 37, 199, 19, 32, 35, 139, 215, 107, 53, 16, 24, 10, 82, 214, 234, 30, 115, 97, 117, 102, 131, 23, 129, 93, 239, 62, 2, 17, 0, 0, 0, 1, 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