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: d046875f862d91a3a64f23417098a59a61d573aaa3a2a29dd3bf27064f60a22e
Tx prefix hash: 5c6dcf0ef5c295eeec048f68d66f3de5573f6311fb24aa40adcb66ddea0e8621
Tx public key: b4494daa45d0f76565f1111d823ce706e2ed71e3bec105473a7ba108a41b9718
| Timestamp: 1779852557 | Timestamp [UTC]: 2026-05-27 03:29:17 | Age [y:d:h:m:s]: 00:021:04:53:02 |
| Block: 2555 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6190 | RingCT/type: yes/0 |
| Extra: 01b4494daa45d0f76565f1111d823ce706e2ed71e3bec105473a7ba108a41b971802090000000226697be300 | ||
1 output(s) for total of 35.013392677198 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4b544cafff131c820318f3a517e50ba85c9f9660e99f53a5e1d83675ae426a69 | 35.013392677198 | 3009 of 0 | <40> |
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": 2615,
"vin": [ {
"gen": {
"height": 2555
}
}
],
"vout": [ {
"amount": 35013392677198,
"target": {
"tagged_key": {
"key": "4b544cafff131c820318f3a517e50ba85c9f9660e99f53a5e1d83675ae426a69",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 180, 73, 77, 170, 69, 208, 247, 101, 101, 241, 17, 29, 130, 60, 231, 6, 226, 237, 113, 227, 190, 193, 5, 71, 58, 123, 161, 8, 164, 27, 151, 24, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}