Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad5962238f00fefce2ba69259e630c0ae477062fff2087b435e6a45d16a610ac

Tx prefix hash: 9536ed15d17950aee36294faadb2469993b39ec7b2bcaae6ec84623ea78f8f5f
Tx public key: 1469caeed4ccce0f5ef0d66b0bcedc8bce9cb50648928ffc97293cb7104757e5
Timestamp: 1697424343 Timestamp [UCT]: 2023-10-16 02:45:43 Age [y:d:h:m:s]: 01:100:10:25:38
Block: 870598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332989 RingCT/type: yes/0
Extra: 011469caeed4ccce0f5ef0d66b0bcedc8bce9cb50648928ffc97293cb7104757e502110000000dfaf35c9c000000000000000000

1 output(s) for total of 0.800474405000 dcy

stealth address amount amount idx
00: de59980fbba7a2679534dd7ba72260acd0bf6b9e144c34381eb3536ec89e8ca4 0.800474405000 1325481 of 0

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": 870608, "vin": [ { "gen": { "height": 870598 } } ], "vout": [ { "amount": 800474405, "target": { "key": "de59980fbba7a2679534dd7ba72260acd0bf6b9e144c34381eb3536ec89e8ca4" } } ], "extra": [ 1, 20, 105, 202, 238, 212, 204, 206, 15, 94, 240, 214, 107, 11, 206, 220, 139, 206, 156, 181, 6, 72, 146, 143, 252, 151, 41, 60, 183, 16, 71, 87, 229, 2, 17, 0, 0, 0, 13, 250, 243, 92, 156, 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