Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e0edf0d6788d6cdda6392369c19ba9d8d59a08da07747d5e4120c64403d6e50

Tx prefix hash: d1457dfbf1beaa7f3ef8ac3041417d17e15e38909b57e9212ee9f46aecbf6bf6
Tx public key: bc1d3bc2f028fc9d36adb9e290abea1eeda5c7b950849d4f342db0fd0eb586db
Timestamp: 1719251044 Timestamp [UCT]: 2024-06-24 17:44:04 Age [y:d:h:m:s]: 00:276:15:50:39
Block: 1051329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197698 RingCT/type: yes/0
Extra: 01bc1d3bc2f028fc9d36adb9e290abea1eeda5c7b950849d4f342db0fd0eb586db0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e857914a2bb809d099d9b4f0132a194046f853c63a34d5253eab9bcb5ac40dcc 0.600000000000 1521640 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": 1051339, "vin": [ { "gen": { "height": 1051329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e857914a2bb809d099d9b4f0132a194046f853c63a34d5253eab9bcb5ac40dcc" } } ], "extra": [ 1, 188, 29, 59, 194, 240, 40, 252, 157, 54, 173, 185, 226, 144, 171, 234, 30, 237, 165, 199, 185, 80, 132, 157, 79, 52, 45, 176, 253, 14, 181, 134, 219, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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