Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 926a3823fcec92dac983e4de6334bda981664c636fa0e96ce2c456259b67dd6e

Tx prefix hash: 1d6a492ea297289dc360200cd1e70b79b068b1ed871917b3b9ccfe46a0b1ba53
Tx public key: 80309f6d7e42fe5b05b8a929ea4b96aecb57c7943ea75f2314de5eb8efb51298
Timestamp: 1713360443 Timestamp [UCT]: 2024-04-17 13:27:23 Age [y:d:h:m:s]: 01:200:15:02:02
Block: 1002507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402043 RingCT/type: yes/0
Extra: 0180309f6d7e42fe5b05b8a929ea4b96aecb57c7943ea75f2314de5eb8efb5129802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e963d8908c3fc61e496f30e46f7dd061b49c51ad2f42cc8b196717a005682d06 0.600000000000 1463023 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": 1002517, "vin": [ { "gen": { "height": 1002507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e963d8908c3fc61e496f30e46f7dd061b49c51ad2f42cc8b196717a005682d06" } } ], "extra": [ 1, 128, 48, 159, 109, 126, 66, 254, 91, 5, 184, 169, 41, 234, 75, 150, 174, 203, 87, 199, 148, 62, 167, 95, 35, 20, 222, 94, 184, 239, 181, 18, 152, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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