Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4332b787273e8324e23fa03f6179909deefd51c0db85c6dae170ce7f26d737

Tx prefix hash: 6a0a32245ba91c76ff3b1c4d8507d9f6a16bbfad5fa91dbed9a11c497b4ec308
Tx public key: 5bfad7d21dccde4987ac2c9e9762a6718f25457f24f83d712c5981c49fcfa74b
Timestamp: 1750898194 Timestamp [UCT]: 2025-06-26 00:36:34 Age [y:d:h:m:s]: 00:141:10:09:48
Block: 1312837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99056 RingCT/type: yes/0
Extra: 015bfad7d21dccde4987ac2c9e9762a6718f25457f24f83d712c5981c49fcfa74b0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dccd91eb3b0ecb737c95fde6e3b7ba5db70e3ba45c75efc3bc9c0b39f936fe52 0.600000000000 1800472 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": 1312847, "vin": [ { "gen": { "height": 1312837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dccd91eb3b0ecb737c95fde6e3b7ba5db70e3ba45c75efc3bc9c0b39f936fe52" } } ], "extra": [ 1, 91, 250, 215, 210, 29, 204, 222, 73, 135, 172, 44, 158, 151, 98, 166, 113, 143, 37, 69, 127, 36, 248, 61, 113, 44, 89, 129, 196, 159, 207, 167, 75, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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