Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d4a11283853415689708d9bc4038c1b6f135bd74af749d6122907f7bae931b

Tx prefix hash: 7e0e44de2da76d17c7ae6a2791070f1930d6e39dff84053be1364ec0dd989321
Tx public key: 0e413e93aebd65cd02d07f5497a54ffa6cfcb70d5d01a1e813acc98fa66c7539
Timestamp: 1721483544 Timestamp [UCT]: 2024-07-20 13:52:24 Age [y:d:h:m:s]: 00:237:14:58:16
Block: 1069857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169750 RingCT/type: yes/0
Extra: 010e413e93aebd65cd02d07f5497a54ffa6cfcb70d5d01a1e813acc98fa66c7539021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 563ce2b29d30c067a9bd2c61509035d0d6a5ff9c881e8001d2a27e4b682b5022 0.600000000000 1541450 of 15

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": 1069867, "vin": [ { "gen": { "height": 1069857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "563ce2b29d30c067a9bd2c61509035d0d6a5ff9c881e8001d2a27e4b682b5022" } } ], "extra": [ 1, 14, 65, 62, 147, 174, 189, 101, 205, 2, 208, 127, 84, 151, 165, 79, 250, 108, 252, 183, 13, 93, 1, 161, 232, 19, 172, 201, 143, 166, 108, 117, 57, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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