Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af74f369ec5ab79ade208f641101042b58751b0db6e5c322aa0a9a093c5be221

Tx prefix hash: 6ae63c6e1176c8b1460a24b1220d94a95327ba60a772a32232e1a0b90af098d9
Tx public key: 9e8e6417a1c735fae6a6a85723114062c39900e5737d0db61f67ae4ed82630ce
Timestamp: 1750844028 Timestamp [UCT]: 2025-06-25 09:33:48 Age [y:d:h:m:s]: 00:148:12:54:11
Block: 1312433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104097 RingCT/type: yes/0
Extra: 019e8e6417a1c735fae6a6a85723114062c39900e5737d0db61f67ae4ed82630ce02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd37bf23f635e430dc969c77242fbb5f3f0de06b0c2b5ca73bdba68587f5357 0.600000000000 1800066 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": 1312443, "vin": [ { "gen": { "height": 1312433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd37bf23f635e430dc969c77242fbb5f3f0de06b0c2b5ca73bdba68587f5357" } } ], "extra": [ 1, 158, 142, 100, 23, 161, 199, 53, 250, 230, 166, 168, 87, 35, 17, 64, 98, 195, 153, 0, 229, 115, 125, 13, 182, 31, 103, 174, 78, 216, 38, 48, 206, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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