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: 1ac0e64b54527a5b509262e34fb44e13c4a9bba7ac839cae79b06db3d8b11b3c
Tx prefix hash: a830bab69a5443ae71f7d68f737efefc8910a58fab5c419b42a69bdac22efdd2
Tx public key: 31d8fc0ce99c377b125c3b8da473538d3bb0d3cf05102b71d4e403d1b8e18386
| Timestamp: 1780683266 | Timestamp [UTC]: 2026-06-05 18:14:26 | Age [y:d:h:m:s]: 00:003:07:21:31 |
| Block: 5322 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2564 | RingCT/type: yes/0 |
| Extra: 0131d8fc0ce99c377b125c3b8da473538d3bb0d3cf05102b71d4e403d1b8e18386020900000002e49593ff00 | ||
1 output(s) for total of 34.829091406526 HMNY
| stealth address | amount | amount idx | tag |
| 00: 040e22488ac67bc8104ea13c7e6dcda310d20c318e3b55676f987c615f69613b | 34.829091406526 | 6751 of 0 | <7a> |
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": 5382,
"vin": [ {
"gen": {
"height": 5322
}
}
],
"vout": [ {
"amount": 34829091406526,
"target": {
"tagged_key": {
"key": "040e22488ac67bc8104ea13c7e6dcda310d20c318e3b55676f987c615f69613b",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 49, 216, 252, 12, 233, 156, 55, 123, 18, 92, 59, 141, 164, 115, 83, 141, 59, 176, 211, 207, 5, 16, 43, 113, 212, 228, 3, 209, 184, 225, 131, 134, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}