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: 8edfa516231798e78d0d4f1f16762a8e702c7a1b50ffbc7f46afe9e267e9c317
Tx prefix hash: bcb4be04c9859cc63c299208baf18eecb401f9da00fae37d543fd93d5d4ec1b3
Tx public key: a3b6f282e1458d58587ea6e47a1a10e7240d1c402edf78f0aef63f843139407d
| Timestamp: 1779443059 | Timestamp [UTC]: 2026-05-22 09:44:19 | Age [y:d:h:m:s]: 00:017:17:05:29 |
| Block: 231 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7689 | RingCT/type: yes/0 |
| Extra: 01a3b6f282e1458d58587ea6e47a1a10e7240d1c402edf78f0aef63f843139407d0209000000014438f87f00 | ||
1 output(s) for total of 35.168940420617 HMNY
| stealth address | amount | amount idx | tag |
| 00: b33e2cba5c5819c606e1acc57876ce1ecbe0fd8cfdcefe6d8a55cbc5c9a956ea | 35.168940420617 | 227 of 0 | <17> |
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": 291,
"vin": [ {
"gen": {
"height": 231
}
}
],
"vout": [ {
"amount": 35168940420617,
"target": {
"tagged_key": {
"key": "b33e2cba5c5819c606e1acc57876ce1ecbe0fd8cfdcefe6d8a55cbc5c9a956ea",
"view_tag": "17"
}
}
}
],
"extra": [ 1, 163, 182, 242, 130, 225, 69, 141, 88, 88, 126, 166, 228, 122, 26, 16, 231, 36, 13, 28, 64, 46, 223, 120, 240, 174, 246, 63, 132, 49, 57, 64, 125, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}