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: b5f3474068cee8e88fc08172a264f6343d9515bca896963c623551d4396e9080
Tx prefix hash: b2f157b22a9785d59566fe745f1befe2d52f998679a86643a8f410e0aa7e1ace
Tx public key: c4fa3c7da0be652ee114988cd20a9cfdfa1e8e5d4bea2501200711e6e1548c0b
| Timestamp: 1780988522 | Timestamp [UTC]: 2026-06-09 07:02:02 | Age [y:d:h:m:s]: 00:000:08:57:42 |
| Block: 8185 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 506 | RingCT/type: yes/0 |
| Extra: 01c4fa3c7da0be652ee114988cd20a9cfdfa1e8e5d4bea2501200711e6e1548c0b020900000001e49593ff00 | ||
1 output(s) for total of 34.639416995708 HMNY
| stealth address | amount | amount idx | tag |
| 00: e2b973ee4bd24a6b456a120185ace8c55a01c844ad8083df51b0a888d421f1a7 | 34.639416995708 | 10135 of 0 | <b4> |
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": 8245,
"vin": [ {
"gen": {
"height": 8185
}
}
],
"vout": [ {
"amount": 34639416995708,
"target": {
"tagged_key": {
"key": "e2b973ee4bd24a6b456a120185ace8c55a01c844ad8083df51b0a888d421f1a7",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 196, 250, 60, 125, 160, 190, 101, 46, 225, 20, 152, 140, 210, 10, 156, 253, 250, 30, 142, 93, 75, 234, 37, 1, 32, 7, 17, 230, 225, 84, 140, 11, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}