Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97ba200d587b3fc80d618cbedcf0898843b4de9a251e06780f9b26fb05f09f59

Tx prefix hash: 40cc7cce4bc32372ef0d1d80455370db9cc1a9bb73e9ac9714357f96156424a5
Tx public key: 865ee4aa9b1d107f9e834e460739e604b1390b4b699e70ce60b2c429595f9e94
Timestamp: 1745463933 Timestamp [UCT]: 2025-04-24 03:05:33 Age [y:d:h:m:s]: 00:281:01:12:59
Block: 1268145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198504 RingCT/type: yes/0
Extra: 01865ee4aa9b1d107f9e834e460739e604b1390b4b699e70ce60b2c429595f9e94021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d492d8b6e65f0bdb41c445c282508d610fbbfde3e1af87ec34f58cda1c6d9914 0.600000000000 1755374 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": 1268155, "vin": [ { "gen": { "height": 1268145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d492d8b6e65f0bdb41c445c282508d610fbbfde3e1af87ec34f58cda1c6d9914" } } ], "extra": [ 1, 134, 94, 228, 170, 155, 29, 16, 127, 158, 131, 78, 70, 7, 57, 230, 4, 177, 57, 11, 75, 105, 158, 112, 206, 96, 178, 196, 41, 89, 95, 158, 148, 2, 17, 0, 0, 0, 3, 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