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: d69f05ea7d62e2cde2b5bd14b7c79d0a89c4c031f852bbc1f531d564bcedd061
Tx prefix hash: 75c9b7f84a4ebb706d9b827b17885e4e3a8321d62f3b2c29c9bc5d760ed6fc88
Tx public key: 2a996094f1ef2c5b91636d8802f2d917da66bb908d68e7df7d1b8aa8ec8dbc65
| Timestamp: 1780857448 | Timestamp [UTC]: 2026-06-07 18:37:28 | Age [y:d:h:m:s]: 00:001:03:47:21 |
| Block: 7585 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 301 | RingCT/type: yes/0 |
| Extra: 012a996094f1ef2c5b91636d8802f2d917da66bb908d68e7df7d1b8aa8ec8dbc65020900000002e49593ff00 | ||
1 output(s) for total of 34.679081392144 HMNY
| stealth address | amount | amount idx | tag |
| 00: c049d68768365a48c933f940eeb9b5963e57503f0ba28df7a116909223670447 | 34.679081392144 | 9369 of 0 | <ab> |
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": 7645,
"vin": [ {
"gen": {
"height": 7585
}
}
],
"vout": [ {
"amount": 34679081392144,
"target": {
"tagged_key": {
"key": "c049d68768365a48c933f940eeb9b5963e57503f0ba28df7a116909223670447",
"view_tag": "ab"
}
}
}
],
"extra": [ 1, 42, 153, 96, 148, 241, 239, 44, 91, 145, 99, 109, 136, 2, 242, 217, 23, 218, 102, 187, 144, 141, 104, 231, 223, 125, 27, 138, 168, 236, 141, 188, 101, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}