Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e80e734ca209410ced6ab68d4cfacc45c93d8c8402fa4d8df03051f38e6bad7

Tx prefix hash: ee5ea507b11a857452496bc60a898f4d9e010e3dbc84cf692cbaca383a8617f1
Tx public key: 3bca7e2484f7f7a1afa30dddadce3570a10cc81070f0cec1af928cbf2e4693e0
Timestamp: 1717955974 Timestamp [UCT]: 2024-06-09 17:59:34 Age [y:d:h:m:s]: 00:295:12:43:01
Block: 1040607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211193 RingCT/type: yes/0
Extra: 013bca7e2484f7f7a1afa30dddadce3570a10cc81070f0cec1af928cbf2e4693e00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2ede4d534fce0e7abd01d55034d02a138bcc4a8b8c9f9c2de611f116e71e159 0.600000000000 1509264 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": 1040617, "vin": [ { "gen": { "height": 1040607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2ede4d534fce0e7abd01d55034d02a138bcc4a8b8c9f9c2de611f116e71e159" } } ], "extra": [ 1, 59, 202, 126, 36, 132, 247, 247, 161, 175, 163, 13, 221, 173, 206, 53, 112, 161, 12, 200, 16, 112, 240, 206, 193, 175, 146, 140, 191, 46, 70, 147, 224, 2, 17, 0, 0, 0, 3, 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