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: 171f3860fc9e472421d4d21a8722f91cf75697ff3f85bead31cf1bb4084b2a04
Tx prefix hash: cc047e3dbb9445a235946c209d7c06102c540548471412952f8ce0c038bfd5dc
Tx public key: d847ae85662fb4d5f7514f1c6b021180f0cac6540c2799d67eb941743837afbf
| Timestamp: 1780733826 | Timestamp [UTC]: 2026-06-06 08:17:06 | Age [y:d:h:m:s]: 00:002:16:29:41 |
| Block: 6343 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1543 | RingCT/type: yes/0 |
| Extra: 01d847ae85662fb4d5f7514f1c6b021180f0cac6540c2799d67eb941743837afbf020900000003e49593ff00 | ||
1 output(s) for total of 34.761331066169 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75be4566a7188c068da2a8717ac54eedee2e920acbd73481a1cbd5d26386e963 | 34.761331066169 | 7830 of 0 | <fa> |
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": 6403,
"vin": [ {
"gen": {
"height": 6343
}
}
],
"vout": [ {
"amount": 34761331066169,
"target": {
"tagged_key": {
"key": "75be4566a7188c068da2a8717ac54eedee2e920acbd73481a1cbd5d26386e963",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 216, 71, 174, 133, 102, 47, 180, 213, 247, 81, 79, 28, 107, 2, 17, 128, 240, 202, 198, 84, 12, 39, 153, 214, 126, 185, 65, 116, 56, 55, 175, 191, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}