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: 2fd2a9bf04c77cab7b5e91a29c69f51b8adfc534bdf1896d937f33c33cb0ead2
Tx prefix hash: 43d777a1874f3f558157cc8b95ecbedab3cfc6b71d7bef05016a5649704e0ff0
Tx public key: 737a99c26b1ac31c4a55d0bf2c22c512f18d0a254a0e58434d37c260b40b66e8
| Timestamp: 1780390791 | Timestamp [UTC]: 2026-06-02 08:59:51 | Age [y:d:h:m:s]: 00:006:14:19:02 |
| Block: 5207 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2679 | RingCT/type: yes/0 |
| Extra: 01737a99c26b1ac31c4a55d0bf2c22c512f18d0a254a0e58434d37c260b40b66e802090000000226697be300 | ||
1 output(s) for total of 34.836731842014 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0871ac6c5e785d2b9e501d5bc80ac81896706e36ef0ac638efe385ec46a7c839 | 34.836731842014 | 6588 of 0 | <39> |
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": 5267,
"vin": [ {
"gen": {
"height": 5207
}
}
],
"vout": [ {
"amount": 34836731842014,
"target": {
"tagged_key": {
"key": "0871ac6c5e785d2b9e501d5bc80ac81896706e36ef0ac638efe385ec46a7c839",
"view_tag": "39"
}
}
}
],
"extra": [ 1, 115, 122, 153, 194, 107, 26, 195, 28, 74, 85, 208, 191, 44, 34, 197, 18, 241, 141, 10, 37, 74, 14, 88, 67, 77, 55, 194, 96, 180, 11, 102, 232, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}