Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62374230770560da945a339d43a5ec861f8cf918d9d75154ae73b3c56c67f808

Tx prefix hash: 820e9cf239e40b5f5257e5c2d01aa01340a5bcb946121bb63ae51d3b757da7a3
Tx public key: c396e23abaf0eea1d324d22eb431df253633367d75f82055f2d1b815bc2c7f4d
Timestamp: 1677339500 Timestamp [UCT]: 2023-02-25 15:38:20 Age [y:d:h:m:s]: 02:094:00:02:24
Block: 704765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588808 RingCT/type: yes/0
Extra: 01c396e23abaf0eea1d324d22eb431df253633367d75f82055f2d1b815bc2c7f4d02110000000174b6d784000000000000000000

1 output(s) for total of 2.836748928000 dcy

stealth address amount amount idx
00: 66d6b16264697885ea6e1603c5398295282568a64acf04d987a0615148378143 2.836748928000 1148442 of 0

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": 704775, "vin": [ { "gen": { "height": 704765 } } ], "vout": [ { "amount": 2836748928, "target": { "key": "66d6b16264697885ea6e1603c5398295282568a64acf04d987a0615148378143" } } ], "extra": [ 1, 195, 150, 226, 58, 186, 240, 238, 161, 211, 36, 210, 46, 180, 49, 223, 37, 54, 51, 54, 125, 117, 248, 32, 85, 242, 209, 184, 21, 188, 44, 127, 77, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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