Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e89fc68aaebb4937227b368870441d21f3cc74b48faf7fa53101f0a4e09fde8

Tx prefix hash: 71c7f5cba3f42e5ddec0c08486bf0b3e2d50ccf13fd364067d1ecc88376fe2b7
Tx public key: 138389381b619880a89dfaaf5b6a530f2753d7aa6908935f592c50e2a3c15cbe
Timestamp: 1649278816 Timestamp [UCT]: 2022-04-06 21:00:16 Age [y:d:h:m:s]: 02:342:18:37:01
Block: 474669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 764548 RingCT/type: yes/0
Extra: 01138389381b619880a89dfaaf5b6a530f2753d7aa6908935f592c50e2a3c15cbe02110000000cd3fcec30000000000000000000

1 output(s) for total of 16.414392013000 dcy

stealth address amount amount idx
00: cb89184d1547a9b206ca94356d6a30a0eb0ffb0fbad589f2b4c396077ab1e059 16.414392013000 894750 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": 474679, "vin": [ { "gen": { "height": 474669 } } ], "vout": [ { "amount": 16414392013, "target": { "key": "cb89184d1547a9b206ca94356d6a30a0eb0ffb0fbad589f2b4c396077ab1e059" } } ], "extra": [ 1, 19, 131, 137, 56, 27, 97, 152, 128, 168, 157, 250, 175, 91, 106, 83, 15, 39, 83, 215, 170, 105, 8, 147, 95, 89, 44, 80, 226, 163, 193, 92, 190, 2, 17, 0, 0, 0, 12, 211, 252, 236, 48, 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