Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d55990c6f70f9aa58ee2d269a708e80529809ad91a34290239a4a80476e27cc5

Tx prefix hash: a80fca52b1d832ec69d623ba6152df68e34bf1036eb2fe9aff52f6df93f00c26
Tx public key: da31bbe2d785a2eede7b01545d38d3b1ce0f5e26ba848ae7bdd25dff3bfafc8e
Timestamp: 1710163444 Timestamp [UCT]: 2024-03-11 13:24:04 Age [y:d:h:m:s]: 01:037:20:01:54
Block: 976016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288035 RingCT/type: yes/0
Extra: 01da31bbe2d785a2eede7b01545d38d3b1ce0f5e26ba848ae7bdd25dff3bfafc8e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39203b5c4112a14e9652fcc50725024081771bb16e5d8ddd713d7d4a03824555 0.600000000000 1435999 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": 976026, "vin": [ { "gen": { "height": 976016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39203b5c4112a14e9652fcc50725024081771bb16e5d8ddd713d7d4a03824555" } } ], "extra": [ 1, 218, 49, 187, 226, 215, 133, 162, 238, 222, 123, 1, 84, 93, 56, 211, 177, 206, 15, 94, 38, 186, 132, 138, 231, 189, 210, 93, 255, 59, 250, 252, 142, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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