Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f039a7129463a94c33680a7dda196f07d0bcf5113e6ac0735a7ad5fe99d7d394

Tx prefix hash: b733c134c094e2447051bfbaf78c55529f494769130d4d9fb3f418831511e88e
Tx public key: c2e53b33788abede2a732af31efb99d840e2a461e162c26ecb8e677c7074b5e9
Timestamp: 1708378013 Timestamp [UCT]: 2024-02-19 21:26:53 Age [y:d:h:m:s]: 00:339:03:58:02
Block: 961198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242756 RingCT/type: yes/0
Extra: 01c2e53b33788abede2a732af31efb99d840e2a461e162c26ecb8e677c7074b5e90211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 124b030e67ad5c394043826075da487772a5e239f3f6e3a200a0abf0be57816f 0.600000000000 1420793 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": 961208, "vin": [ { "gen": { "height": 961198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "124b030e67ad5c394043826075da487772a5e239f3f6e3a200a0abf0be57816f" } } ], "extra": [ 1, 194, 229, 59, 51, 120, 138, 190, 222, 42, 115, 42, 243, 30, 251, 153, 216, 64, 226, 164, 97, 225, 98, 194, 110, 203, 142, 103, 124, 112, 116, 181, 233, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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