Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b0c0b8500ff76ea47538a83a1767d3531f1edf98502917dc07d8c9827cf2487

Tx prefix hash: 688d22d9cdc4f2435b53f80008729bc3adc170399d5f185a1422c8b06fb4a68c
Tx public key: e8aaa5e6c99c678191e4b4b7e0eb93a34ab2b684509bf419579a0a79dc7a10f2
Timestamp: 1750438830 Timestamp [UCT]: 2025-06-20 17:00:30 Age [y:d:h:m:s]: 00:153:22:24:46
Block: 1309181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107852 RingCT/type: yes/0
Extra: 01e8aaa5e6c99c678191e4b4b7e0eb93a34ab2b684509bf419579a0a79dc7a10f2021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1650b6fe33f7552f937c5b6d10d967dad3e8df494fdd53e5aa2853f266c9c0e 0.600000000000 1796796 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": 1309191, "vin": [ { "gen": { "height": 1309181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1650b6fe33f7552f937c5b6d10d967dad3e8df494fdd53e5aa2853f266c9c0e" } } ], "extra": [ 1, 232, 170, 165, 230, 201, 156, 103, 129, 145, 228, 180, 183, 224, 235, 147, 163, 74, 178, 182, 132, 80, 155, 244, 25, 87, 154, 10, 121, 220, 122, 16, 242, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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