Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a94f4c544a23a75f8312b6fa83314d684232026b98975f99a758d7d355668dca

Tx prefix hash: 69a822467ea378a980bd039ae053ac0186f8253886a22cfc3b5ae93b21bf1ebe
Tx public key: 076a19da9326c26ec876e0e278aa9a813583f8afbdd2695681c927c8ab38b8e2
Timestamp: 1720743538 Timestamp [UCT]: 2024-07-12 00:18:58 Age [y:d:h:m:s]: 01:130:13:49:35
Block: 1063728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351843 RingCT/type: yes/0
Extra: 01076a19da9326c26ec876e0e278aa9a813583f8afbdd2695681c927c8ab38b8e202110000001391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c5edda6a39db0094b59b45fbdb2d24b51b798a708558ed598e76ae97122f245 0.600000000000 1534245 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": 1063738, "vin": [ { "gen": { "height": 1063728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c5edda6a39db0094b59b45fbdb2d24b51b798a708558ed598e76ae97122f245" } } ], "extra": [ 1, 7, 106, 25, 218, 147, 38, 194, 110, 200, 118, 224, 226, 120, 170, 154, 129, 53, 131, 248, 175, 189, 210, 105, 86, 129, 201, 39, 200, 171, 56, 184, 226, 2, 17, 0, 0, 0, 19, 145, 225, 60, 4, 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