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: 55c5323f5386e8b1775b85a5e019815d40c196895692a98b7be8bb581aef4304
Tx prefix hash: f07a4e8e610a808b92c1f1c2736218c617179c600e087a8e99bcdaa78632a9c3
Tx public key: 37683dc39572162bdee8b1379d0df922a75af80d704346e0620a2b58c9f61253
| Timestamp: 1780749977 | Timestamp [UTC]: 2026-06-06 12:46:17 | Age [y:d:h:m:s]: 00:002:10:32:36 |
| Block: 6485 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1401 | RingCT/type: yes/0 |
| Extra: 0137683dc39572162bdee8b1379d0df922a75af80d704346e0620a2b58c9f61253020900000001e49593ff00 | ||
1 output(s) for total of 34.751917451283 HMNY
| stealth address | amount | amount idx | tag |
| 00: 79e57d0c469736d64aac039dbfc28dea11087b08e25b223403f7b7a09b6114b7 | 34.751917451283 | 7980 of 0 | <fd> |
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": 6545,
"vin": [ {
"gen": {
"height": 6485
}
}
],
"vout": [ {
"amount": 34751917451283,
"target": {
"tagged_key": {
"key": "79e57d0c469736d64aac039dbfc28dea11087b08e25b223403f7b7a09b6114b7",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 55, 104, 61, 195, 149, 114, 22, 43, 222, 232, 177, 55, 157, 13, 249, 34, 167, 90, 248, 13, 112, 67, 70, 224, 98, 10, 43, 88, 201, 246, 18, 83, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}