Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da4df7d9f73c25467687abc45d4ed88b1f7665d88507a227d01810d04c62077c

Tx prefix hash: c0a6135e20384c97c8ce67a5f5f0de75e33df158e612e7654895499de3453d44
Tx public key: 751b5fb3e574ffe20a1fa815b4dfacd2a7a3562556eebd81f12ece39bab87153
Timestamp: 1643504509 Timestamp [UCT]: 2022-01-30 01:01:49 Age [y:d:h:m:s]: 03:275:20:51:07
Block: 428143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 974061 RingCT/type: yes/0
Extra: 01751b5fb3e574ffe20a1fa815b4dfacd2a7a3562556eebd81f12ece39bab87153021100000003d3fcec30000000000000000000

1 output(s) for total of 23.409105622000 dcy

stealth address amount amount idx
00: 0e0e8e41e888cac14dd57a0e375829781b2fe0f64dbb6dc44632f8e93b0f1bd0 23.409105622000 837465 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": 428153, "vin": [ { "gen": { "height": 428143 } } ], "vout": [ { "amount": 23409105622, "target": { "key": "0e0e8e41e888cac14dd57a0e375829781b2fe0f64dbb6dc44632f8e93b0f1bd0" } } ], "extra": [ 1, 117, 27, 95, 179, 229, 116, 255, 226, 10, 31, 168, 21, 180, 223, 172, 210, 167, 163, 86, 37, 86, 238, 189, 129, 241, 46, 206, 57, 186, 184, 113, 83, 2, 17, 0, 0, 0, 3, 211, 252, 236, 48, 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