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: f84d4f25d0485edd439dafb49d3840d8af27180988c6e349bb0ca9349704298a
Tx prefix hash: f99c71e4848ab72e664c0e9feb0d13c706810b116942bef5872a46cc64f72166
Tx public key: 122fba3c7c64f85b1a5cf95df51d6237e79a0304a58fc44296c7192cc267dd3c
| Timestamp: 1780690157 | Timestamp [UTC]: 2026-06-05 20:09:17 | Age [y:d:h:m:s]: 00:003:05:26:40 |
| Block: 5639 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2247 | RingCT/type: yes/0 |
| Extra: 01122fba3c7c64f85b1a5cf95df51d6237e79a0304a58fc44296c7192cc267dd3c020900000001e49593ff00 | ||
1 output(s) for total of 34.808039054826 HMNY
| stealth address | amount | amount idx | tag |
| 00: 748cd766fcb1925a123c66ee344e7ec6bfb26b984a2ecacbf1a8cfa457c97f79 | 34.808039054826 | 7086 of 0 | <e2> |
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": 5699,
"vin": [ {
"gen": {
"height": 5639
}
}
],
"vout": [ {
"amount": 34808039054826,
"target": {
"tagged_key": {
"key": "748cd766fcb1925a123c66ee344e7ec6bfb26b984a2ecacbf1a8cfa457c97f79",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 18, 47, 186, 60, 124, 100, 248, 91, 26, 92, 249, 93, 245, 29, 98, 55, 231, 154, 3, 4, 165, 143, 196, 66, 150, 199, 25, 44, 194, 103, 221, 60, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}