Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84ede797b8b0d6e315dd682a4d64b8b1cc44cbbd0750d7e9880c3adb73638170

Tx prefix hash: c5ec268a944e1b0b86bc183c8d10df43d52ea917599bc0b4b38881e3afd6b87e
Tx public key: 43b9113e756b00116dae1ad246c051717fd89743c8460f44ed7d09036fe9f69f
Timestamp: 1735398433 Timestamp [UCT]: 2024-12-28 15:07:13 Age [y:d:h:m:s]: 00:092:11:19:14
Block: 1185078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65883 RingCT/type: yes/0
Extra: 0143b9113e756b00116dae1ad246c051717fd89743c8460f44ed7d09036fe9f69f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6eb8e293a1ea50661d4fb97ac924716543126dc300692ad4c6cfaa71298a175 0.600000000000 1671543 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": 1185088, "vin": [ { "gen": { "height": 1185078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6eb8e293a1ea50661d4fb97ac924716543126dc300692ad4c6cfaa71298a175" } } ], "extra": [ 1, 67, 185, 17, 62, 117, 107, 0, 17, 109, 174, 26, 210, 70, 192, 81, 113, 127, 216, 151, 67, 200, 70, 15, 68, 237, 125, 9, 3, 111, 233, 246, 159, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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