Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e532ddaed9ded15ea3c68ee9f6a7065e1626c31594567dfee69d1285ae276ba

Tx prefix hash: 3d9b7f3025330f9956dc2cd8ee5eddf1cd0a6152621789a9ebde79743d2f4daf
Tx public key: a87a4e475c05917caefa40c7685df04101f2029b3f046a1aed7ee890794787d3
Timestamp: 1742146351 Timestamp [UCT]: 2025-03-16 17:32:31 Age [y:d:h:m:s]: 00:234:12:23:08
Block: 1240708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165304 RingCT/type: yes/0
Extra: 01a87a4e475c05917caefa40c7685df04101f2029b3f046a1aed7ee890794787d302110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a3eb98df9b750efb0829f8fb237eb243fbf7937fa022b2333456e651fc33933 0.600000000000 1727681 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": 1240718, "vin": [ { "gen": { "height": 1240708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a3eb98df9b750efb0829f8fb237eb243fbf7937fa022b2333456e651fc33933" } } ], "extra": [ 1, 168, 122, 78, 71, 92, 5, 145, 124, 174, 250, 64, 199, 104, 93, 240, 65, 1, 242, 2, 155, 63, 4, 106, 26, 237, 126, 232, 144, 121, 71, 135, 211, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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