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: d68efb9abb26fa84622ee6e08ec6d77a1a750191a240b1d67b2fb53b4d6211a4
Tx prefix hash: a4972f5eee96ea9b152db3a6892c9c4bf46ae051481a23608541976180df62e6
Tx public key: 871743edcf09530a692e328ee5931698fc91a4a135e77aa8d386d0f9e222ebcd
| Timestamp: 1779846341 | Timestamp [UTC]: 2026-05-27 01:45:41 | Age [y:d:h:m:s]: 00:017:09:16:35 |
| Block: 2458 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6287 | RingCT/type: yes/0 |
| Extra: 01871743edcf09530a692e328ee5931698fc91a4a135e77aa8d386d0f9e222ebcd02090000000226697be300 | ||
1 output(s) for total of 35.019871209089 HMNY
| stealth address | amount | amount idx | tag |
| 00: fdda660f55f213e6ff92c9caf428b6c72563d913977a34e7dd67a7c02fac87cc | 35.019871209089 | 2890 of 0 | <ea> |
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": 2518,
"vin": [ {
"gen": {
"height": 2458
}
}
],
"vout": [ {
"amount": 35019871209089,
"target": {
"tagged_key": {
"key": "fdda660f55f213e6ff92c9caf428b6c72563d913977a34e7dd67a7c02fac87cc",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 135, 23, 67, 237, 207, 9, 83, 10, 105, 46, 50, 142, 229, 147, 22, 152, 252, 145, 164, 161, 53, 231, 122, 168, 211, 134, 208, 249, 226, 34, 235, 205, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}