Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 513aee703d5504f542f719dc9972889f1dd4664a662c00bb64bf69c25eb62181

Tx prefix hash: 0f0a5c7248e2678214ca53fce24d2e0cdf4b4162d4b571e8340fa2b0610128a0
Tx public key: d0a8807c2b6870bbe89f21980df5b00ccd1589352268086ff2e4fdb509d3de70
Timestamp: 1699107154 Timestamp [UCT]: 2023-11-04 14:12:34 Age [y:d:h:m:s]: 02:030:17:59:55
Block: 884596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541540 RingCT/type: yes/0
Extra: 01d0a8807c2b6870bbe89f21980df5b00ccd1589352268086ff2e4fdb509d3de7002110000000ffaf35c9c000000000000000000

1 output(s) for total of 0.719393061000 dcy

stealth address amount amount idx
00: 441d35bfbb8690ce34fdbd31d309f5c52f864c624a19d37bd44671f7831e90dc 0.719393061000 1340341 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": 884606, "vin": [ { "gen": { "height": 884596 } } ], "vout": [ { "amount": 719393061, "target": { "key": "441d35bfbb8690ce34fdbd31d309f5c52f864c624a19d37bd44671f7831e90dc" } } ], "extra": [ 1, 208, 168, 128, 124, 43, 104, 112, 187, 232, 159, 33, 152, 13, 245, 176, 12, 205, 21, 137, 53, 34, 104, 8, 111, 242, 228, 253, 181, 9, 211, 222, 112, 2, 17, 0, 0, 0, 15, 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