Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0894ea7cb304338e91edf1e9f5d1b852695c053e6f025305920c082eb3ccf64

Tx prefix hash: 77b3b13c8ec35aa11bfba9888ce82b5f962be3a7b4be9362595411958426e164
Tx public key: 8a117ec8364f6623c36db34558c8e7c56571ea0014b3a2eb5626a54e7d400e78
Timestamp: 1703432736 Timestamp [UCT]: 2023-12-24 15:45:36 Age [y:d:h:m:s]: 01:346:20:12:39
Block: 920206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506769 RingCT/type: yes/0
Extra: 018a117ec8364f6623c36db34558c8e7c56571ea0014b3a2eb5626a54e7d400e780211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e3d9115461bb84eac10e5b1e163e3435cb068f6db2aec48c62737685c37faf 0.600000000000 1377884 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": 920216, "vin": [ { "gen": { "height": 920206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e3d9115461bb84eac10e5b1e163e3435cb068f6db2aec48c62737685c37faf" } } ], "extra": [ 1, 138, 17, 126, 200, 54, 79, 102, 35, 195, 109, 179, 69, 88, 200, 231, 197, 101, 113, 234, 0, 20, 179, 162, 235, 86, 38, 165, 78, 125, 64, 14, 120, 2, 17, 0, 0, 0, 2, 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