Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82f2289c39d4029fa15f16e89747d117e27a663fb2c4d51de19ff931a12e1033

Tx prefix hash: ddab06b9a0b4bf59e1abf6886f480930b69d91bd79a1dbc5b7d3951dd289c8f5
Tx public key: ac1d431d3463fdeee6a840fd221260a38fc645a0e942f5d3ce465aea3aa9236c
Timestamp: 1705927683 Timestamp [UCT]: 2024-01-22 12:48:03 Age [y:d:h:m:s]: 01:295:22:11:18
Block: 940856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470334 RingCT/type: yes/0
Extra: 01ac1d431d3463fdeee6a840fd221260a38fc645a0e942f5d3ce465aea3aa9236c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74fc8216fed2b61708d25042991481e4a20a8345524604fe184af519ec897b15 0.600000000000 1398996 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": 940866, "vin": [ { "gen": { "height": 940856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74fc8216fed2b61708d25042991481e4a20a8345524604fe184af519ec897b15" } } ], "extra": [ 1, 172, 29, 67, 29, 52, 99, 253, 238, 230, 168, 64, 253, 34, 18, 96, 163, 143, 198, 69, 160, 233, 66, 245, 211, 206, 70, 90, 234, 58, 169, 35, 108, 2, 17, 0, 0, 0, 4, 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