Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960a0dd00b360be9c1a25413aa91d3a9b99567f0453652b5d2165f3ba06db5c4

Tx prefix hash: 0592a207442e7ce428d07806a911360a64e88130d8e0ad758426d588d6f7dd0d
Tx public key: 3757636912e16c62626dd9d639937ab5e1aa94e6bb30e4bf9b6bd46eac133fff
Timestamp: 1581703302 Timestamp [UCT]: 2020-02-14 18:01:42 Age [y:d:h:m:s]: 05:090:13:41:45
Block: 65214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1217384 RingCT/type: yes/0
Extra: 013757636912e16c62626dd9d639937ab5e1aa94e6bb30e4bf9b6bd46eac133fff021100000001724f989b000000000000000000

1 output(s) for total of 373.187640165000 dcy

stealth address amount amount idx
00: 4e494006d3815c3eba968fac7920bb6ff2daae21f6169654579d0b4cc4e0d870 373.187640165000 120227 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": 65224, "vin": [ { "gen": { "height": 65214 } } ], "vout": [ { "amount": 373187640165, "target": { "key": "4e494006d3815c3eba968fac7920bb6ff2daae21f6169654579d0b4cc4e0d870" } } ], "extra": [ 1, 55, 87, 99, 105, 18, 225, 108, 98, 98, 109, 217, 214, 57, 147, 122, 181, 225, 170, 148, 230, 187, 48, 228, 191, 155, 107, 212, 110, 172, 19, 63, 255, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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