Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e83ed3e82420310c3bff5272cf19c8bb04f333a1fea3704faaed07d5e0bf0cd1

Tx prefix hash: 5d59c88f05291578a6cf584c7c848693e8f2c1290feff702c3093f55ee878bb5
Tx public key: f198e6dea54b4dc11ccb69ca36f162addd9e2243d93d961cbe24fb4f1481fe71
Timestamp: 1721648601 Timestamp [UCT]: 2024-07-22 11:43:21 Age [y:d:h:m:s]: 00:240:06:17:33
Block: 1071219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171646 RingCT/type: yes/0
Extra: 01f198e6dea54b4dc11ccb69ca36f162addd9e2243d93d961cbe24fb4f1481fe7102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9fdf5786fe30f2bf0f26b3486352df64ba1ce96d27b304e27a7d36796f17857 0.600000000000 1543356 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": 1071229, "vin": [ { "gen": { "height": 1071219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9fdf5786fe30f2bf0f26b3486352df64ba1ce96d27b304e27a7d36796f17857" } } ], "extra": [ 1, 241, 152, 230, 222, 165, 75, 77, 193, 28, 203, 105, 202, 54, 241, 98, 173, 221, 158, 34, 67, 217, 61, 150, 28, 190, 36, 251, 79, 20, 129, 254, 113, 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