Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ab0483ea8b6bc124f830761f63ebfd27e54e9afe2a3d32b4fb0786783df695

Tx prefix hash: 16a1d613c5d4ebcf64b22090894b7fcd428a9620c0f7a8f860c9c39facce0b37
Tx public key: 4bad3c0d5927f91656ac7a3bc5ef57bbdcac57d9dba49ca661f5966be6067a29
Timestamp: 1683685458 Timestamp [UCT]: 2023-05-10 02:24:18 Age [y:d:h:m:s]: 02:008:00:14:32
Block: 756747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527845 RingCT/type: yes/0
Extra: 014bad3c0d5927f91656ac7a3bc5ef57bbdcac57d9dba49ca661f5966be6067a2902110000000375e3f0e9000000000000000000

1 output(s) for total of 1.908021401000 dcy

stealth address amount amount idx
00: 6f2361950eacf99cd4aceb1ee1b5d928d00c551acf63dc9e079ef035ede738ba 1.908021401000 1205136 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": 756757, "vin": [ { "gen": { "height": 756747 } } ], "vout": [ { "amount": 1908021401, "target": { "key": "6f2361950eacf99cd4aceb1ee1b5d928d00c551acf63dc9e079ef035ede738ba" } } ], "extra": [ 1, 75, 173, 60, 13, 89, 39, 249, 22, 86, 172, 122, 59, 197, 239, 87, 187, 220, 172, 87, 217, 219, 164, 156, 166, 97, 245, 150, 107, 230, 6, 122, 41, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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