Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abdaefacc23ffc6c95075bd5438c0523c4b6524760b593c964d9444ee9779202

Tx prefix hash: 31e9f3f413c95133320dfd5897c5cedb651d11d7957c5301cf905a4231a5613f
Tx public key: 7625d3431f8461c7fc6a19d14f4bd4b3bab1c68b4f688dc035bcc22aa68bf0e5
Timestamp: 1703622855 Timestamp [UCT]: 2023-12-26 20:34:15 Age [y:d:h:m:s]: 01:086:22:34:56
Block: 921781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323251 RingCT/type: yes/0
Extra: 017625d3431f8461c7fc6a19d14f4bd4b3bab1c68b4f688dc035bcc22aa68bf0e502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 260ece6de8cb307f02c75a279959f94193d6425e31834fa0db8af5f3efce157c 0.600000000000 1379475 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": 921791, "vin": [ { "gen": { "height": 921781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "260ece6de8cb307f02c75a279959f94193d6425e31834fa0db8af5f3efce157c" } } ], "extra": [ 1, 118, 37, 211, 67, 31, 132, 97, 199, 252, 106, 25, 209, 79, 75, 212, 179, 186, 177, 198, 139, 79, 104, 141, 192, 53, 188, 194, 42, 166, 139, 240, 229, 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