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: e1df9ff32e49e50bc1b971c863a2deef47d82aadb09f7dcb6ea2b85000d034f4
Tx prefix hash: d5616d212955e000f4174dd03de42cb3d735c99e826ea2fa48a53e9c1d367667
Tx public key: fea8a988a971ea14c727eb0f0fc10d9a3bc3f773966dfe81c0dd3c040bed9d1f
| Timestamp: 1780836911 | Timestamp [UTC]: 2026-06-07 12:55:11 | Age [y:d:h:m:s]: 00:001:08:16:56 |
| Block: 7421 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 465 | RingCT/type: yes/0 |
| Extra: 01fea8a988a971ea14c727eb0f0fc10d9a3bc3f773966dfe81c0dd3c040bed9d1f020900000001e49593ff00 | ||
1 output(s) for total of 34.689930895444 HMNY
| stealth address | amount | amount idx | tag |
| 00: efcbd33d486cdb2c8447733a62d8030466f26019ef7cbba844cb179cc81e6619 | 34.689930895444 | 9137 of 0 | <cf> |
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": 7481,
"vin": [ {
"gen": {
"height": 7421
}
}
],
"vout": [ {
"amount": 34689930895444,
"target": {
"tagged_key": {
"key": "efcbd33d486cdb2c8447733a62d8030466f26019ef7cbba844cb179cc81e6619",
"view_tag": "cf"
}
}
}
],
"extra": [ 1, 254, 168, 169, 136, 169, 113, 234, 20, 199, 39, 235, 15, 15, 193, 13, 154, 59, 195, 247, 115, 150, 109, 254, 129, 192, 221, 60, 4, 11, 237, 157, 31, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}