Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f702bd9a2c82f211fc3a431a0b8bf3e0b80fa45011431a626839fa36c84cbf7

Tx prefix hash: 9ea05aa78d24c2adafadc643682d3a1c00672156c9258ce0d12c5783d8e169a6
Tx public key: c72453a8cfd135d349e8136792cd61ef66f8271f012de413938b16de827fb782
Timestamp: 1754699302 Timestamp [UCT]: 2025-08-09 00:28:22 Age [y:d:h:m:s]: 00:012:18:04:59
Block: 1343156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8292 RingCT/type: yes/0
Extra: 01c72453a8cfd135d349e8136792cd61ef66f8271f012de413938b16de827fb782021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b96f227349b4a47243cf9921ffb8c9fbd980b1d3d3bf3ba7d8c4e6dd0b6e6dfe 0.600000000000 1830991 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": 1343166, "vin": [ { "gen": { "height": 1343156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b96f227349b4a47243cf9921ffb8c9fbd980b1d3d3bf3ba7d8c4e6dd0b6e6dfe" } } ], "extra": [ 1, 199, 36, 83, 168, 207, 209, 53, 211, 73, 232, 19, 103, 146, 205, 97, 239, 102, 248, 39, 31, 1, 45, 228, 19, 147, 139, 22, 222, 130, 127, 183, 130, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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