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: 3ea8b3d1d765c6ac0fc88d114dd25110d4714f859a871d54e29652bda19c5bd2
Tx prefix hash: 9c2381f8e2d4abc9b63e5fba96ea2e9872634f1de3fd5d9c679d26b251b74c2b
Tx public key: 98d6a21973f3c8c65378a32cb72d0848bd188a2a65ce85a11a6e0e072b17af7e
| Timestamp: 1780703791 | Timestamp [UTC]: 2026-06-05 23:56:31 | Age [y:d:h:m:s]: 00:002:23:22:22 |
| Block: 6082 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1804 | RingCT/type: yes/0 |
| Extra: 0198d6a21973f3c8c65378a32cb72d0848bd188a2a65ce85a11a6e0e072b17af7e020900000002e49593ff00 | ||
1 output(s) for total of 34.778640206791 HMNY
| stealth address | amount | amount idx | tag |
| 00: f4c6d76d3aa5290651bf23f5d6bd6bcab4a6ce5a3eb538583e71157b0a1ea550 | 34.778640206791 | 7553 of 0 | <96> |
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": 6142,
"vin": [ {
"gen": {
"height": 6082
}
}
],
"vout": [ {
"amount": 34778640206791,
"target": {
"tagged_key": {
"key": "f4c6d76d3aa5290651bf23f5d6bd6bcab4a6ce5a3eb538583e71157b0a1ea550",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 152, 214, 162, 25, 115, 243, 200, 198, 83, 120, 163, 44, 183, 45, 8, 72, 189, 24, 138, 42, 101, 206, 133, 161, 26, 110, 14, 7, 43, 23, 175, 126, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}