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: 5e34e03879e9e15e3b52429e7cd93650a3a344e16972521ef26f141936bdf396
Tx prefix hash: 66172cc0115c00dc40c5afa78dfa308e0e755a83545f9f59442660438bbb5455
Tx public key: 1d3d73c26d55d8ee1935aeb9a846651a33d2d3c628d80f1e5934663630fef24b
| Timestamp: 1779466865 | Timestamp [UTC]: 2026-05-22 16:21:05 | Age [y:d:h:m:s]: 00:017:10:28:43 |
| Block: 522 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7378 | RingCT/type: yes/0 |
| Extra: 011d3d73c26d55d8ee1935aeb9a846651a33d2d3c628d80f1e5934663630fef24b02090000000193369e7d00 | ||
1 output(s) for total of 35.149425703961 HMNY
| stealth address | amount | amount idx | tag |
| 00: d6c9f3f6fcd60dbf994a5ce962b6bcde5c82939843bf6890cf07497a1ed2b184 | 35.149425703961 | 526 of 0 | <b3> |
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": 582,
"vin": [ {
"gen": {
"height": 522
}
}
],
"vout": [ {
"amount": 35149425703961,
"target": {
"tagged_key": {
"key": "d6c9f3f6fcd60dbf994a5ce962b6bcde5c82939843bf6890cf07497a1ed2b184",
"view_tag": "b3"
}
}
}
],
"extra": [ 1, 29, 61, 115, 194, 109, 85, 216, 238, 25, 53, 174, 185, 168, 70, 101, 26, 51, 210, 211, 198, 40, 216, 15, 30, 89, 52, 102, 54, 48, 254, 242, 75, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}