Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 923c132377c79a6d4bdda5975f9b61496eca1c3deabbcb8b185e81445b2dd4ed

Tx prefix hash: b02a06683632ab739d7fcb888310071ee440b53a80fbc877df8bcac4e3c052c3
Tx public key: e18dbd5409893d75ffc0d6ab3a277aba1bef920ea5448b731b76b86f1d87d8fc
Timestamp: 1582433979 Timestamp [UCT]: 2020-02-23 04:59:39 Age [y:d:h:m:s]: 04:327:13:13:50
Block: 70582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126758 RingCT/type: yes/0
Extra: 01e18dbd5409893d75ffc0d6ab3a277aba1bef920ea5448b731b76b86f1d87d8fc021100000002c71d3ff9000000000000000000

1 output(s) for total of 358.206396546000 dcy

stealth address amount amount idx
00: 3efafa3fb747f15a1e8c5c9553ce9c2fb270a1caaa6858e22270e71df80ba691 358.206396546000 130432 of 0

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": 70592, "vin": [ { "gen": { "height": 70582 } } ], "vout": [ { "amount": 358206396546, "target": { "key": "3efafa3fb747f15a1e8c5c9553ce9c2fb270a1caaa6858e22270e71df80ba691" } } ], "extra": [ 1, 225, 141, 189, 84, 9, 137, 61, 117, 255, 192, 214, 171, 58, 39, 122, 186, 27, 239, 146, 14, 165, 68, 139, 115, 27, 118, 184, 111, 29, 135, 216, 252, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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