Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ec7f937289534a05f257ec47d4e82665b6e458dfe6ca39ad594019d3c4bcc0

Tx prefix hash: d8cdc091d71eb6cb5f2b97fbfb9c9236f48b9eed121c4fc28bfad1a5dec844e0
Tx public key: 9884998569c06876e140d2a1ef19cbf92879703d0edb97d18b39c5a3ff3da11a
Timestamp: 1704649452 Timestamp [UCT]: 2024-01-07 17:44:12 Age [y:d:h:m:s]: 01:004:12:20:06
Block: 930273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264566 RingCT/type: yes/0
Extra: 019884998569c06876e140d2a1ef19cbf92879703d0edb97d18b39c5a3ff3da11a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21b5c652fe41909beb7234d37aee62464392356811b1ae9d5da700d28107ac2a 0.600000000000 1388155 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": 930283, "vin": [ { "gen": { "height": 930273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21b5c652fe41909beb7234d37aee62464392356811b1ae9d5da700d28107ac2a" } } ], "extra": [ 1, 152, 132, 153, 133, 105, 192, 104, 118, 225, 64, 210, 161, 239, 25, 203, 249, 40, 121, 112, 61, 14, 219, 151, 209, 139, 57, 197, 163, 255, 61, 161, 26, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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