Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f97eb70f24324dba513cf3a0812ee547fec0b1057bb6777d922f89ccb87e5f8

Tx prefix hash: 025cdd5d0b1526ba22ec87b658f7b99ab75c168a003d0f47065aeee6fe47e4b1
Tx public key: d3a09506ad4dcb92ff345c796fc379d065d76cf02f4576dd917d3b5d70802a23
Timestamp: 1723413513 Timestamp [UCT]: 2024-08-11 21:58:33 Age [y:d:h:m:s]: 00:167:11:53:47
Block: 1085852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119781 RingCT/type: yes/0
Extra: 01d3a09506ad4dcb92ff345c796fc379d065d76cf02f4576dd917d3b5d70802a23021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed4c8ab6d0a19cbe8ea538640b82cc30f632ed6a609af2184143d2d171ae475e 0.600000000000 1560443 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": 1085862, "vin": [ { "gen": { "height": 1085852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed4c8ab6d0a19cbe8ea538640b82cc30f632ed6a609af2184143d2d171ae475e" } } ], "extra": [ 1, 211, 160, 149, 6, 173, 77, 203, 146, 255, 52, 92, 121, 111, 195, 121, 208, 101, 215, 108, 240, 47, 69, 118, 221, 145, 125, 59, 93, 112, 128, 42, 35, 2, 17, 0, 0, 0, 8, 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