Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9698e94e1750ee132d07e695c3a4493fd9f28b52a7554dea532ad88457afa668

Tx prefix hash: c7d59d0c7c83d8b47361d39b48b7510294efb01968ffa0251a166257a4074cab
Tx public key: c56b35f86d82a05e0aa11037d147df244b6e58197e00926d4a2fc766d8cb9e15
Timestamp: 1756010836 Timestamp [UCT]: 2025-08-24 04:47:16 Age [y:d:h:m:s]: 00:094:10:25:04
Block: 1353178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67439 RingCT/type: yes/0
Extra: 01c56b35f86d82a05e0aa11037d147df244b6e58197e00926d4a2fc766d8cb9e1502110000000bad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9941e6c91076cea530c89ce2acd3f5603021347a2214d5d1daddd0f7c44c352f 0.600000000000 1841151 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": 1353188, "vin": [ { "gen": { "height": 1353178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9941e6c91076cea530c89ce2acd3f5603021347a2214d5d1daddd0f7c44c352f" } } ], "extra": [ 1, 197, 107, 53, 248, 109, 130, 160, 94, 10, 161, 16, 55, 209, 71, 223, 36, 75, 110, 88, 25, 126, 0, 146, 109, 74, 47, 199, 102, 216, 203, 158, 21, 2, 17, 0, 0, 0, 11, 173, 121, 72, 208, 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