Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5766a88d6ff0eed8dc865f28f0466d5ba8cb8469bc1bf43bc3a7f673b47a686

Tx prefix hash: 34bb8a19d186c4a93b14eea1c6caf4af2344c09ce40db2cbdd4fe4ba2ef1d93c
Tx public key: a772a4867ef480d97b00919de60e1d295732cf111396c7ee15bf5a5c84bcf3b6
Timestamp: 1747067058 Timestamp [UCT]: 2025-05-12 16:24:18 Age [y:d:h:m:s]: 00:184:14:00:48
Block: 1281420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129625 RingCT/type: yes/0
Extra: 01a772a4867ef480d97b00919de60e1d295732cf111396c7ee15bf5a5c84bcf3b602110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1c1c136a1c3717a303852ce93c97830d355ee4f46b428b897f40d051f407cb0 0.600000000000 1768819 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": 1281430, "vin": [ { "gen": { "height": 1281420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1c1c136a1c3717a303852ce93c97830d355ee4f46b428b897f40d051f407cb0" } } ], "extra": [ 1, 167, 114, 164, 134, 126, 244, 128, 217, 123, 0, 145, 157, 230, 14, 29, 41, 87, 50, 207, 17, 19, 150, 199, 238, 21, 191, 90, 92, 132, 188, 243, 182, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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