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: a200c60f0e4ec72c039e1309725b89250b1eb2e2638f653ff4b21cf0be311bcc
Tx prefix hash: 8e2c517369a01d87025888b4370550d585fa0513062422c300adf06bfb07be8c
Tx public key: 46c607e6bcce45b88ab2c202b61f424c76941ccdab2b17a9ebb2fb176aaacff9
| Timestamp: 1780079603 | Timestamp [UTC]: 2026-05-29 18:33:23 | Age [y:d:h:m:s]: 00:010:07:02:34 |
| Block: 4745 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3141 | RingCT/type: yes/0 |
| Extra: 0146c607e6bcce45b88ab2c202b61f424c76941ccdab2b17a9ebb2fb176aaacff902090000000226697be300 | ||
1 output(s) for total of 34.867443357030 HMNY
| stealth address | amount | amount idx | tag |
| 00: e390d1e3c4f0afefb7aeabf41d014d4165e1a635adcf9ca93a598184d843d76b | 34.867443357030 | 5964 of 0 | <d1> |
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": 4805,
"vin": [ {
"gen": {
"height": 4745
}
}
],
"vout": [ {
"amount": 34867443357030,
"target": {
"tagged_key": {
"key": "e390d1e3c4f0afefb7aeabf41d014d4165e1a635adcf9ca93a598184d843d76b",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 70, 198, 7, 230, 188, 206, 69, 184, 138, 178, 194, 2, 182, 31, 66, 76, 118, 148, 28, 205, 171, 43, 23, 169, 235, 178, 251, 23, 106, 170, 207, 249, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}