Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3cabdda910e3e926e3fbae5eb22545400c41198aa882d70ee600826d7b7c1a7

Tx prefix hash: aa3222cc1f6bcd84d75b2d2f64a680fbbd6304894da667a5ec1c01a6273644a8
Tx public key: afdc8a9ae6fbefbb31972db6832a2660c1b24cea23a1ce9896120a70df11a81a
Timestamp: 1744891264 Timestamp [UCT]: 2025-04-17 12:01:04 Age [y:d:h:m:s]: 00:288:16:04:29
Block: 1263407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203952 RingCT/type: yes/0
Extra: 01afdc8a9ae6fbefbb31972db6832a2660c1b24cea23a1ce9896120a70df11a81a021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64bfc90d679d276538bc276e42092000c22300b99b61aca4ef1dc5044573d8f 0.600000000000 1750598 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": 1263417, "vin": [ { "gen": { "height": 1263407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64bfc90d679d276538bc276e42092000c22300b99b61aca4ef1dc5044573d8f" } } ], "extra": [ 1, 175, 220, 138, 154, 230, 251, 239, 187, 49, 151, 45, 182, 131, 42, 38, 96, 193, 178, 76, 234, 35, 161, 206, 152, 150, 18, 10, 112, 223, 17, 168, 26, 2, 17, 0, 0, 0, 2, 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