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: bbc187029b24f134da39020f6ba3b30eda6d838a5a8edf0c3b92c4ad87d04a2f
Tx prefix hash: ef8a7f0c65ba8ffc9d92d666822173a139941d62cf283198d770d1f6bc987f7c
Tx public key: c77a05ce69e15decd75b3c74d2a2b3113768853b15ab5e096e4bae5bb05aa0c7
| Timestamp: 1780693011 | Timestamp [UTC]: 2026-06-05 20:56:51 | Age [y:d:h:m:s]: 00:003:04:39:06 |
| Block: 5835 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2051 | RingCT/type: yes/0 |
| Extra: 01c77a05ce69e15decd75b3c74d2a2b3113768853b15ab5e096e4bae5bb05aa0c7020900000001e49593ff00 | ||
1 output(s) for total of 34.795028825567 HMNY
| stealth address | amount | amount idx | tag |
| 00: 065ac086f3ef214816e0dfcb169ce9c646d5f5b4dd57659d22ac5fc79c78a6ee | 34.795028825567 | 7292 of 0 | <d1> |
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": 5895,
"vin": [ {
"gen": {
"height": 5835
}
}
],
"vout": [ {
"amount": 34795028825567,
"target": {
"tagged_key": {
"key": "065ac086f3ef214816e0dfcb169ce9c646d5f5b4dd57659d22ac5fc79c78a6ee",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 199, 122, 5, 206, 105, 225, 93, 236, 215, 91, 60, 116, 210, 162, 179, 17, 55, 104, 133, 59, 21, 171, 94, 9, 110, 75, 174, 91, 176, 90, 160, 199, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}