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: ecaa5e45369c350d5d94f82be9bb344bd14ecad07cf840b79e15cebb45e7c579
Tx prefix hash: f034470502f00d9812e7efc93fd0e390f263b7499b4449b2d14546fb45b0a52e
Tx public key: 5cce1e401aa1596ddfd64679f916c82bd26d1316c87d865ef7b51cd30eff3af3
| Timestamp: 1780828074 | Timestamp [UTC]: 2026-06-07 10:27:54 | Age [y:d:h:m:s]: 00:009:22:01:18 |
| Block: 7299 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1446 | RingCT/type: yes/0 |
| Extra: 015cce1e401aa1596ddfd64679f916c82bd26d1316c87d865ef7b51cd30eff3af3020900000001e49593ff00 | ||
1 output(s) for total of 34.698004069063 HMNY
| stealth address | amount | amount idx | tag |
| 00: 57bd8af0ab4ec002af10fd7481623397c9d1e4d7904cae01b97627dabc445d44 | 34.698004069063 | 8985 of 0 | <d1> |
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": 7359,
"vin": [ {
"gen": {
"height": 7299
}
}
],
"vout": [ {
"amount": 34698004069063,
"target": {
"tagged_key": {
"key": "57bd8af0ab4ec002af10fd7481623397c9d1e4d7904cae01b97627dabc445d44",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 92, 206, 30, 64, 26, 161, 89, 109, 223, 214, 70, 121, 249, 22, 200, 43, 210, 109, 19, 22, 200, 125, 134, 94, 247, 181, 28, 211, 14, 255, 58, 243, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}