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: 36e5a5ff2b7adcfbc19e3ce7ccfdfc7b014138999a7e8ed3d9735ff8ae7f2f7c
Tx prefix hash: 8fc8bc7a3f95b24b7fed0697c6e73cacd55930db3f9e127a5fc107c664cb485a
Tx public key: d10b633a88a68ac65ef2c9f6b1aacf819fa13bdd155a65d1a5c6641f4df59f47
| Timestamp: 1780719453 | Timestamp [UTC]: 2026-06-06 04:17:33 | Age [y:d:h:m:s]: 00:003:12:51:30 |
| Block: 6228 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2505 | RingCT/type: yes/0 |
| Extra: 01d10b633a88a68ac65ef2c9f6b1aacf819fa13bdd155a65d1a5c6641f4df59f47020900000005e49593ff00 | ||
1 output(s) for total of 34.768956637114 HMNY
| stealth address | amount | amount idx | tag |
| 00: 01e4854d01d8236e0bc335692dd632f2cea3b21a37f9dc66f1716cb7ca41d531 | 34.768956637114 | 7707 of 0 | <0b> |
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": 6288,
"vin": [ {
"gen": {
"height": 6228
}
}
],
"vout": [ {
"amount": 34768956637114,
"target": {
"tagged_key": {
"key": "01e4854d01d8236e0bc335692dd632f2cea3b21a37f9dc66f1716cb7ca41d531",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 209, 11, 99, 58, 136, 166, 138, 198, 94, 242, 201, 246, 177, 170, 207, 129, 159, 161, 59, 221, 21, 90, 101, 209, 165, 198, 100, 31, 77, 245, 159, 71, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}