Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38968a4950384f64fe25159aa9bcd4d8bf44656bce3bcf633dc9487738f1026c

Tx prefix hash: ab0bb956a69a26483676942bf4ad5cc481a1d5bdf47e6c1f32668473cd9e46f4
Tx public key: a0e7738625b25453e0f4aec83d8a99006f027d8b52910657b4c4cfb92e0da2ac
Timestamp: 1762591381 Timestamp [UCT]: 2025-11-08 08:43:01 Age [y:d:h:m:s]: 00:083:21:26:38
Block: 1407540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59874 RingCT/type: yes/0
Extra: 01a0e7738625b25453e0f4aec83d8a99006f027d8b52910657b4c4cfb92e0da2ac021100000009dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52bc244cfeb3e489db178d031eeb11aa9ed790e974d70c5459745cbcbec4ae20 0.600000000000 1895961 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": 1407550, "vin": [ { "gen": { "height": 1407540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52bc244cfeb3e489db178d031eeb11aa9ed790e974d70c5459745cbcbec4ae20" } } ], "extra": [ 1, 160, 231, 115, 134, 37, 178, 84, 83, 224, 244, 174, 200, 61, 138, 153, 0, 111, 2, 125, 139, 82, 145, 6, 87, 180, 196, 207, 185, 46, 13, 162, 172, 2, 17, 0, 0, 0, 9, 223, 195, 186, 73, 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