Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320318daa81c6a4b502519d416aa0cbc29deadc0595395c3232b09b288930b9f

Tx prefix hash: 3a56d2b67738310fb198f49d5ca4fec954a10dd93eaf22e3cc49c8b5b24819c3
Tx public key: 4c8ae1b257eed0154f182a1b3188a34b6aa65434bec40530fed32a7cccc1ee1d
Timestamp: 1732557539 Timestamp [UCT]: 2024-11-25 17:58:59 Age [y:d:h:m:s]: 00:361:23:45:19
Block: 1161562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256254 RingCT/type: yes/0
Extra: 014c8ae1b257eed0154f182a1b3188a34b6aa65434bec40530fed32a7cccc1ee1d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7cb18a99ab84eaeff79440845a012784d52183baf4ac555931451218de2a933 0.600000000000 1647217 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": 1161572, "vin": [ { "gen": { "height": 1161562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7cb18a99ab84eaeff79440845a012784d52183baf4ac555931451218de2a933" } } ], "extra": [ 1, 76, 138, 225, 178, 87, 238, 208, 21, 79, 24, 42, 27, 49, 136, 163, 75, 106, 166, 84, 52, 190, 196, 5, 48, 254, 211, 42, 124, 204, 193, 238, 29, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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