Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda6d3dbe62e01f4c18dbba801d64b37cf0acf52fecbb6bc34eb4ec6182bbb35

Tx prefix hash: 4a8cb781e57fa9f2bf9d58ae604d6aa83f467ff3e2095bcef30289fbd205161a
Tx public key: eac5a088f7e9cbb9e7b500e5d642ae23a1ba522e6d0787faebb6f90061c74f8d
Timestamp: 1698143883 Timestamp [UCT]: 2023-10-24 10:38:03 Age [y:d:h:m:s]: 01:164:06:46:16
Block: 876566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378422 RingCT/type: yes/0
Extra: 01eac5a088f7e9cbb9e7b500e5d642ae23a1ba522e6d0787faebb6f90061c74f8d02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.764844204000 dcy

stealth address amount amount idx
00: 6125b7859aa8a4dcddf41de69418cd678fca2ff4d808f1b4cc9fea9920c4fb85 0.764844204000 1331896 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": 876576, "vin": [ { "gen": { "height": 876566 } } ], "vout": [ { "amount": 764844204, "target": { "key": "6125b7859aa8a4dcddf41de69418cd678fca2ff4d808f1b4cc9fea9920c4fb85" } } ], "extra": [ 1, 234, 197, 160, 136, 247, 233, 203, 185, 231, 181, 0, 229, 214, 66, 174, 35, 161, 186, 82, 46, 109, 7, 135, 250, 235, 182, 249, 0, 97, 199, 79, 141, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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