Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad2aab6b002623ad3ac5c0d020d162e4cb65f33131668348af25de23255c8039

Tx prefix hash: db6502cb85ed3a2f71db7e51ee8f4d2736c5108897a07e9a9c9c3c72e434ad1b
Tx public key: affe6cc5080f83b0024a6c1addab0c5795e3b69ded8fc5b8e6cbf77197a8a1dc
Timestamp: 1582972508 Timestamp [UCT]: 2020-02-29 10:35:08 Age [y:d:h:m:s]: 04:343:11:03:40
Block: 73937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138969 RingCT/type: yes/0
Extra: 01affe6cc5080f83b0024a6c1addab0c5795e3b69ded8fc5b8e6cbf77197a8a1dc021100000225c71d3ff9000000000000000000

1 output(s) for total of 349.153841881000 dcy

stealth address amount amount idx
00: f18b8b9ab69efd9a1c81d26ecc46deee8260f3a398fb6650b44987d5eadffc44 349.153841881000 136638 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": 73947, "vin": [ { "gen": { "height": 73937 } } ], "vout": [ { "amount": 349153841881, "target": { "key": "f18b8b9ab69efd9a1c81d26ecc46deee8260f3a398fb6650b44987d5eadffc44" } } ], "extra": [ 1, 175, 254, 108, 197, 8, 15, 131, 176, 2, 74, 108, 26, 221, 171, 12, 87, 149, 227, 182, 157, 237, 143, 197, 184, 230, 203, 247, 113, 151, 168, 161, 220, 2, 17, 0, 0, 2, 37, 199, 29, 63, 249, 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