Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de3674d94f64b8bf58ab45d2c1d4b5d28f363c59818c9eeea5809898bf3c2e3e

Tx prefix hash: d4b67736cce3310d22d5a54bf382decb93d158c6c59f2a88e60220d22c3a102f
Tx public key: 6fe403614b1c88e447ebb1c667e3477acb34c622d4794de3d407fb9187503025
Timestamp: 1751809501 Timestamp [UCT]: 2025-07-06 13:45:01 Age [y:d:h:m:s]: 00:183:08:31:04
Block: 1319953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129535 RingCT/type: yes/0
Extra: 016fe403614b1c88e447ebb1c667e3477acb34c622d4794de3d407fb9187503025021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0e1a98961ab838f837053a7a92eb6e0298d053a310ec4cc237987a5e294f5c 0.600000000000 1807648 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": 1319963, "vin": [ { "gen": { "height": 1319953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0e1a98961ab838f837053a7a92eb6e0298d053a310ec4cc237987a5e294f5c" } } ], "extra": [ 1, 111, 228, 3, 97, 75, 28, 136, 228, 71, 235, 177, 198, 103, 227, 71, 122, 203, 52, 198, 34, 212, 121, 77, 227, 212, 7, 251, 145, 135, 80, 48, 37, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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