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: fb8134be360f170e73b4e5816a30cc3cee1929d6860a7495d08a6917a3c62b6d
Tx prefix hash: b36a7ad8f3d4c403c28e8e9816e70d5db499bd6dfd0d2cf3a11822ed9b1359cc
Tx public key: 5b81c922d7a0b22d1de7c4ef00d77c20f87eb0f7145eaa8294d93dc09f77b576
| Timestamp: 1780833390 | Timestamp [UTC]: 2026-06-07 11:56:30 | Age [y:d:h:m:s]: 00:001:09:15:37 |
| Block: 7368 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 518 | RingCT/type: yes/0 |
| Extra: 015b81c922d7a0b22d1de7c4ef00d77c20f87eb0f7145eaa8294d93dc09f77b576020900000001e49593ff00 | ||
1 output(s) for total of 34.693437863034 HMNY
| stealth address | amount | amount idx | tag |
| 00: b0112cff591b5b5bb9882311dc33bca8c8631b521e46d41fdd57d12dfb69c2a3 | 34.693437863034 | 9072 of 0 | <17> |
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": 7428,
"vin": [ {
"gen": {
"height": 7368
}
}
],
"vout": [ {
"amount": 34693437863034,
"target": {
"tagged_key": {
"key": "b0112cff591b5b5bb9882311dc33bca8c8631b521e46d41fdd57d12dfb69c2a3",
"view_tag": "17"
}
}
}
],
"extra": [ 1, 91, 129, 201, 34, 215, 160, 178, 45, 29, 231, 196, 239, 0, 215, 124, 32, 248, 126, 176, 247, 20, 94, 170, 130, 148, 217, 61, 192, 159, 119, 181, 118, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}