Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61e94b8468ab7408eaf189a6417ed946e73fc809c6cbdc0b801f8f77e881684c

Tx prefix hash: eaff2fc445a4eb72826b77c4e5b3aa76a470544d3ae5a30439f86828e2f7a2f1
Tx public key: c3f64fac056d74423d3367adf0291326b83cb15704f79a886bc9e17e10e4a5b7
Timestamp: 1581698930 Timestamp [UCT]: 2020-02-14 16:48:50 Age [y:d:h:m:s]: 04:322:22:11:13
Block: 64911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123035 RingCT/type: yes/0
Extra: 01c3f64fac056d74423d3367adf0291326b83cb15704f79a886bc9e17e10e4a5b702110000000256c366d3000000000000000000

1 output(s) for total of 374.044886792000 dcy

stealth address amount amount idx
00: 9ff5655d36e6cbb608c5f61c9c13ec9f03283370e2a53254c13c95c4301262f4 374.044886792000 119821 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": 64921, "vin": [ { "gen": { "height": 64911 } } ], "vout": [ { "amount": 374044886792, "target": { "key": "9ff5655d36e6cbb608c5f61c9c13ec9f03283370e2a53254c13c95c4301262f4" } } ], "extra": [ 1, 195, 246, 79, 172, 5, 109, 116, 66, 61, 51, 103, 173, 240, 41, 19, 38, 184, 60, 177, 87, 4, 247, 154, 136, 107, 201, 225, 126, 16, 228, 165, 183, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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