For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 3e58ce351a2028620f5d2748519b04f1d2cb6373e5dea2b4f24ddf714dd8935d
Tx prefix hash: 4ea83e7606f1f8c0cf21c742c3f97b3c303303a144b4d7daf32391f528866407
Tx public key: 513d7e9245e5e21be3fb2f996a2d5e89327224dd5a3533fb962a45d44707026f
| Timestamp: 1780814717 | Timestamp [UTC]: 2026-06-07 06:45:17 | Age [y:d:h:m:s]: 00:001:18:50:40 |
| Block: 7043 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 843 | RingCT/type: yes/0 |
| Extra: 01513d7e9245e5e21be3fb2f996a2d5e89327224dd5a3533fb962a45d44707026f020900000001e49593ff00 | ||
1 output(s) for total of 34.714950607025 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7fb49fcc7bb27a8244cacb8247051a03d82f3abe2707334b1ab2583ba360c88 | 34.714950607025 | 8685 of 0 | <b7> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 7103,
"vin": [ {
"gen": {
"height": 7043
}
}
],
"vout": [ {
"amount": 34714950607025,
"target": {
"tagged_key": {
"key": "b7fb49fcc7bb27a8244cacb8247051a03d82f3abe2707334b1ab2583ba360c88",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 81, 61, 126, 146, 69, 229, 226, 27, 227, 251, 47, 153, 106, 45, 94, 137, 50, 114, 36, 221, 90, 53, 51, 251, 150, 42, 69, 212, 71, 7, 2, 111, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}