Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361ccb96f1a490dcfac5e56d03df827fb7806205f5747209bb1ec5896b3782cf

Tx prefix hash: fffebcdf366cc3a496e00526cb01c818577e24d4424f95ab11c6fde5aa18ea20
Tx public key: 82ef71ed08a3e6a3b458e10ffd0971503cdf7881d3e4249130f3e0d13906a15a
Timestamp: 1745667384 Timestamp [UCT]: 2025-04-26 11:36:24 Age [y:d:h:m:s]: 00:207:20:25:05
Block: 1269844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146261 RingCT/type: yes/0
Extra: 0182ef71ed08a3e6a3b458e10ffd0971503cdf7881d3e4249130f3e0d13906a15a02110000000bdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48479a7d51d2bc8ff5f0c97c08da48fb71a3da50b49fbb6f81984bd23daa3d6b 0.600000000000 1757083 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": 1269854, "vin": [ { "gen": { "height": 1269844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48479a7d51d2bc8ff5f0c97c08da48fb71a3da50b49fbb6f81984bd23daa3d6b" } } ], "extra": [ 1, 130, 239, 113, 237, 8, 163, 230, 163, 180, 88, 225, 15, 253, 9, 113, 80, 60, 223, 120, 129, 211, 228, 36, 145, 48, 243, 224, 209, 57, 6, 161, 90, 2, 17, 0, 0, 0, 11, 219, 181, 113, 193, 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