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: 37c47b05b56813b45e5e0dba803142c098122ad2f9de7ee61f7ce37505e926a6
Tx prefix hash: 4489f4b6ab5157241757ae5b8e48f4b17912f32650710460b47361c4d1a9f9c5
Tx public key: 95bd274936f26dbcc78c03f6a88201b050841bf1860d6cefb25374b6572a8135
| Timestamp: 1779445272 | Timestamp [UTC]: 2026-05-22 10:21:12 | Age [y:d:h:m:s]: 00:017:16:28:36 |
| Block: 269 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7631 | RingCT/type: yes/0 |
| Extra: 0195bd274936f26dbcc78c03f6a88201b050841bf1860d6cefb25374b6572a81350209000000014438f87f00 | ||
1 output(s) for total of 35.166391492203 HMNY
| stealth address | amount | amount idx | tag |
| 00: dcb9c33f5d37322b9fc08c09c414f8aa087165293b82040ee6e3c069430ecb45 | 35.166391492203 | 265 of 0 | <c2> |
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": 329,
"vin": [ {
"gen": {
"height": 269
}
}
],
"vout": [ {
"amount": 35166391492203,
"target": {
"tagged_key": {
"key": "dcb9c33f5d37322b9fc08c09c414f8aa087165293b82040ee6e3c069430ecb45",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 149, 189, 39, 73, 54, 242, 109, 188, 199, 140, 3, 246, 168, 130, 1, 176, 80, 132, 27, 241, 134, 13, 108, 239, 178, 83, 116, 182, 87, 42, 129, 53, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}