Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e76bc37f7219bc794a1cadeb1b79048a14dc181979d082f63a8dc57e20016fd7

Tx prefix hash: 1ec8f59247109bf9e07c69657450340620106dd2f854f10c2b8c8359f365e289
Tx public key: 28a557a1e1a41e828c9b61b51ef99dd5bc46be021b36f5e52dd269eb18dae3a7
Timestamp: 1577974031 Timestamp [UCT]: 2020-01-02 14:07:11 Age [y:d:h:m:s]: 04:329:06:22:11
Block: 37262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124374 RingCT/type: yes/0
Extra: 0128a557a1e1a41e828c9b61b51ef99dd5bc46be021b36f5e52dd269eb18dae3a702110000000ed81c26c0000000000000000000

1 output(s) for total of 461.887678994000 dcy

stealth address amount amount idx
00: 70c99b5cc6b54ef66859b17d4fd242a22785156bc7a9c46e8d6bac5b1678ad46 461.887678994000 63186 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": 37272, "vin": [ { "gen": { "height": 37262 } } ], "vout": [ { "amount": 461887678994, "target": { "key": "70c99b5cc6b54ef66859b17d4fd242a22785156bc7a9c46e8d6bac5b1678ad46" } } ], "extra": [ 1, 40, 165, 87, 161, 225, 164, 30, 130, 140, 155, 97, 181, 30, 249, 157, 213, 188, 70, 190, 2, 27, 54, 245, 229, 45, 210, 105, 235, 24, 218, 227, 167, 2, 17, 0, 0, 0, 14, 216, 28, 38, 192, 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