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: 94d60effbe6d3e09d7467c2520ddb64469469aee734adf9f4d8e921b5f9ef198
Tx prefix hash: 8a252ec79a15bea71bdeb300e410c880dd66e41cfc14430464249df7d4feb51d
Tx public key: da203180fe9461b8fa132e251d339e6854466f4decf6c0a322c982b57f9d809c
| Timestamp: 1779785321 | Timestamp [UTC]: 2026-05-26 08:48:41 | Age [y:d:h:m:s]: 00:013:16:47:16 |
| Block: 2156 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5730 | RingCT/type: yes/0 |
| Extra: 01da203180fe9461b8fa132e251d339e6854466f4decf6c0a322c982b57f9d809c02090000000126697be300 | ||
1 output(s) for total of 35.045057960467 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3c4dc3cd1d698f12968894a6c9661b9731319227ada499ad9cf33a2c2b01d37a | 35.045057960467 | 2488 of 0 | <34> |
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": 2216,
"vin": [ {
"gen": {
"height": 2156
}
}
],
"vout": [ {
"amount": 35045057960467,
"target": {
"tagged_key": {
"key": "3c4dc3cd1d698f12968894a6c9661b9731319227ada499ad9cf33a2c2b01d37a",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 218, 32, 49, 128, 254, 148, 97, 184, 250, 19, 46, 37, 29, 51, 158, 104, 84, 70, 111, 77, 236, 246, 192, 163, 34, 201, 130, 181, 127, 157, 128, 156, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}