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: 095c27776042440cca549f7ddd0354627b2477daeacc5355e0d4ba7c8c2be70c
Tx prefix hash: 5cfd676e5dff7d24a90fe3d5d3dc635ba057c421d08e3cf16cfaa5022cc59148
Tx public key: 8db1d7e11cfabd7f65c45193cdd4d9357fcd88496b38f2a87768ef45cac86827
| Timestamp: 1780018202 | Timestamp [UTC]: 2026-05-29 01:30:02 | Age [y:d:h:m:s]: 00:010:23:16:45 |
| Block: 4130 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3756 | RingCT/type: yes/0 |
| Extra: 018db1d7e11cfabd7f65c45193cdd4d9357fcd88496b38f2a87768ef45cac8682702090000000a26697be300 | ||
1 output(s) for total of 34.908367581627 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2347e338e84e6485e07331500a3805032db1a0cb2b87367c8b48089ac1c48149 | 34.908367581627 | 5157 of 0 | <c9> |
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": 4190,
"vin": [ {
"gen": {
"height": 4130
}
}
],
"vout": [ {
"amount": 34908367581627,
"target": {
"tagged_key": {
"key": "2347e338e84e6485e07331500a3805032db1a0cb2b87367c8b48089ac1c48149",
"view_tag": "c9"
}
}
}
],
"extra": [ 1, 141, 177, 215, 225, 28, 250, 189, 127, 101, 196, 81, 147, 205, 212, 217, 53, 127, 205, 136, 73, 107, 56, 242, 168, 119, 104, 239, 69, 202, 200, 104, 39, 2, 9, 0, 0, 0, 10, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}