Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a68bb560985afdac6fbbae8a6bc8ae18238d12002a159a244f3ab4abe0906a2

Tx prefix hash: 375e06fecbb9f29b218cf86a81bda85283c683e1ddc61657c41f0d1e5d674e1a
Tx public key: c8cffef2273b434aa5dd96c04d63ca0aed3ecfd665e27c341edba764b7745fe3
Timestamp: 1720241918 Timestamp [UCT]: 2024-07-06 04:58:38 Age [y:d:h:m:s]: 00:251:19:51:53
Block: 1059558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179933 RingCT/type: yes/0
Extra: 01c8cffef2273b434aa5dd96c04d63ca0aed3ecfd665e27c341edba764b7745fe30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11ee241da107348532e9f4452df715baf4e2b8cd90d13598767a6e8fa1394e7f 0.600000000000 1530027 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": 1059568, "vin": [ { "gen": { "height": 1059558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11ee241da107348532e9f4452df715baf4e2b8cd90d13598767a6e8fa1394e7f" } } ], "extra": [ 1, 200, 207, 254, 242, 39, 59, 67, 74, 165, 221, 150, 192, 77, 99, 202, 10, 237, 62, 207, 214, 101, 226, 124, 52, 30, 219, 167, 100, 183, 116, 95, 227, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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