Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ba5f5ce04334d8abc10f8d0689dfe65b0b5eff16012bc82ad59ab8ce72d3e5a

Tx prefix hash: edce853cad02afc279bcb3b7f448e8478a02dbd0bffa0d9a32650ec8514b6589
Tx public key: f1571ddfe5b79abb663b48dcdb938cdd7f6d73103e39ed625c9b782756a243cc
Timestamp: 1720662685 Timestamp [UCT]: 2024-07-11 01:51:25 Age [y:d:h:m:s]: 00:270:15:21:10
Block: 1063055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193341 RingCT/type: yes/0
Extra: 01f1571ddfe5b79abb663b48dcdb938cdd7f6d73103e39ed625c9b782756a243cc021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e30ca791dba17e0b1adae257e5b3f185ed035aa5d9f6870e558794bc423a2ebd 0.600000000000 1533568 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": 1063065, "vin": [ { "gen": { "height": 1063055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30ca791dba17e0b1adae257e5b3f185ed035aa5d9f6870e558794bc423a2ebd" } } ], "extra": [ 1, 241, 87, 29, 223, 229, 183, 154, 187, 102, 59, 72, 220, 219, 147, 140, 221, 127, 109, 115, 16, 62, 57, 237, 98, 92, 155, 120, 39, 86, 162, 67, 204, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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