Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4167483822eef64fe5aabea6074830e8d61649a18f951e5aacb4f4971b25fcd

Tx prefix hash: b69699aaf7bdce2c2ec6452b350f64c644e084176de0ef750b5231e1e3b1b96b
Tx public key: 5a416a080ab5b14b4aab2672839557f002ecf2f777a4cefc90ca012ceecc7725
Timestamp: 1582189597 Timestamp [UCT]: 2020-02-20 09:06:37 Age [y:d:h:m:s]: 04:317:09:56:15
Block: 68621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119442 RingCT/type: yes/0
Extra: 015a416a080ab5b14b4aab2672839557f002ecf2f777a4cefc90ca012ceecc77250211000000027adf42d3000000000000000000

1 output(s) for total of 363.605921050000 dcy

stealth address amount amount idx
00: d46db87f72fc244eca0b6793d00a4384c759d38f744519b60aa6fdf9b884b003 363.605921050000 126522 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": 68631, "vin": [ { "gen": { "height": 68621 } } ], "vout": [ { "amount": 363605921050, "target": { "key": "d46db87f72fc244eca0b6793d00a4384c759d38f744519b60aa6fdf9b884b003" } } ], "extra": [ 1, 90, 65, 106, 8, 10, 181, 177, 75, 74, 171, 38, 114, 131, 149, 87, 240, 2, 236, 242, 247, 119, 164, 206, 252, 144, 202, 1, 44, 238, 204, 119, 37, 2, 17, 0, 0, 0, 2, 122, 223, 66, 211, 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