Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea65739ca90fdd22a187cbad15a04d876d35ac5ccf7de86198c273a71a1b16c

Tx prefix hash: 07b7a6a0810856893e424b6d4b165367917fd63b90090ec51c5ff43e13fc2f28
Tx public key: 34e1b69cea90aa9b8b9a8912076a668c70c7b78b239ebda7e469551ba25d3e9e
Timestamp: 1721419963 Timestamp [UCT]: 2024-07-19 20:12:43 Age [y:d:h:m:s]: 01:112:05:17:24
Block: 1069363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338668 RingCT/type: yes/0
Extra: 0134e1b69cea90aa9b8b9a8912076a668c70c7b78b239ebda7e469551ba25d3e9e0211000000020bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da4f219f43638ac03d2838cefb7b616771d13aac92634bb9df7bbd8793ff3061 0.600000000000 1540752 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": 1069373, "vin": [ { "gen": { "height": 1069363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da4f219f43638ac03d2838cefb7b616771d13aac92634bb9df7bbd8793ff3061" } } ], "extra": [ 1, 52, 225, 182, 156, 234, 144, 170, 155, 139, 154, 137, 18, 7, 106, 102, 140, 112, 199, 183, 139, 35, 158, 189, 167, 228, 105, 85, 27, 162, 93, 62, 158, 2, 17, 0, 0, 0, 2, 11, 186, 22, 215, 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