Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af0d20e1d1af01b1543a0b4042c13dc8ba42372c3ca252cfcdf835580eddc480

Tx prefix hash: 3849d4c578d65d96381931149c1bf49700e65557aaaa72179f0a5810224c583d
Tx public key: 6a8990eb1c97a94c4b0cf1687b720e7bf8dfb0fc71e639399f531bc1bce4a721
Timestamp: 1754139360 Timestamp [UCT]: 2025-08-02 12:56:00 Age [y:d:h:m:s]: 00:020:06:38:05
Block: 1338745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13446 RingCT/type: yes/0
Extra: 016a8990eb1c97a94c4b0cf1687b720e7bf8dfb0fc71e639399f531bc1bce4a7210211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb726bb2f203e6724cc101f1b34d1d9daca47039b09e77fd7f330201e0d495f7 0.600000000000 1826554 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": 1338755, "vin": [ { "gen": { "height": 1338745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb726bb2f203e6724cc101f1b34d1d9daca47039b09e77fd7f330201e0d495f7" } } ], "extra": [ 1, 106, 137, 144, 235, 28, 151, 169, 76, 75, 12, 241, 104, 123, 114, 14, 123, 248, 223, 176, 252, 113, 230, 57, 57, 159, 83, 27, 193, 188, 228, 167, 33, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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