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: fc878f702339a51772d9f786580aefc437e813061f0b8e2cd7e2bb9e2ca1d5e1
Tx prefix hash: 0683c2eb5ef245e453f8e20bfeaddfef7ab8f08c2286dc92144f02301c8f5592
Tx public key: dc49e0cf8d2ed70c2d3c6f4a1840d659de0f250082c3da6c40b8ad039a71d5aa
| Timestamp: 1780692181 | Timestamp [UTC]: 2026-06-05 20:43:01 | Age [y:d:h:m:s]: 00:003:06:06:47 |
| Block: 5777 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2143 | RingCT/type: yes/0 |
| Extra: 01dc49e0cf8d2ed70c2d3c6f4a1840d659de0f250082c3da6c40b8ad039a71d5aa020900000001e49593ff00 | ||
1 output(s) for total of 34.798878284698 HMNY
| stealth address | amount | amount idx | tag |
| 00: b423eabd10f1a3af7458c68d896f210d0dd33fa372b0c87d8e554c589920738c | 34.798878284698 | 7232 of 0 | <ca> |
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": 5837,
"vin": [ {
"gen": {
"height": 5777
}
}
],
"vout": [ {
"amount": 34798878284698,
"target": {
"tagged_key": {
"key": "b423eabd10f1a3af7458c68d896f210d0dd33fa372b0c87d8e554c589920738c",
"view_tag": "ca"
}
}
}
],
"extra": [ 1, 220, 73, 224, 207, 141, 46, 215, 12, 45, 60, 111, 74, 24, 64, 214, 89, 222, 15, 37, 0, 130, 195, 218, 108, 64, 184, 173, 3, 154, 113, 213, 170, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}