Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6169ba5729e79c7bdf5928fdfbe168983d3001a2d19f3e0d86fdcf1cc47314ae

Tx prefix hash: 7d5549e13e403db4798fad49bf716ba928c24707f22834014d228979bc6ddede
Tx public key: 3dc8a2dbb92fee9d8460135ab146719c8de1c63b3f87e9cb98c4af353135f9e4
Timestamp: 1721176116 Timestamp [UCT]: 2024-07-17 00:28:36 Age [y:d:h:m:s]: 00:315:02:11:12
Block: 1067322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225147 RingCT/type: yes/0
Extra: 013dc8a2dbb92fee9d8460135ab146719c8de1c63b3f87e9cb98c4af353135f9e402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02d3959176656e674acf37a85e47aeb741431bff6cf4a8786fb5d0c84635ad4b 0.600000000000 1538103 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": 1067332, "vin": [ { "gen": { "height": 1067322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02d3959176656e674acf37a85e47aeb741431bff6cf4a8786fb5d0c84635ad4b" } } ], "extra": [ 1, 61, 200, 162, 219, 185, 47, 238, 157, 132, 96, 19, 90, 177, 70, 113, 156, 141, 225, 198, 59, 63, 135, 233, 203, 152, 196, 175, 53, 49, 53, 249, 228, 2, 17, 0, 0, 0, 5, 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