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: 995b5c7ce7c2a557a82d01a0e43f55acbe45282b201e0b19f551271a395d216e
Tx prefix hash: 33b651135e21fa25c87d751e9ce9f983a9c4d9a1b3c66015f0ad6011b1fc64e5
Tx public key: 10bbf1b805cb783d54123bac7f9a9a42a8ddddc28738b40ebd16905899bdf4cb
| Timestamp: 1780689508 | Timestamp [UTC]: 2026-06-05 19:58:28 | Age [y:d:h:m:s]: 00:003:04:48:19 |
| Block: 5600 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2286 | RingCT/type: yes/0 |
| Extra: 0110bbf1b805cb783d54123bac7f9a9a42a8ddddc28738b40ebd16905899bdf4cb020900000001e49593ff00 | ||
1 output(s) for total of 34.810628405163 HMNY
| stealth address | amount | amount idx | tag |
| 00: bcea4e71273b467ef90b55798e71d5daff676de3719f69248b209072d98cdb39 | 34.810628405163 | 7045 of 0 | <49> |
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": 5660,
"vin": [ {
"gen": {
"height": 5600
}
}
],
"vout": [ {
"amount": 34810628405163,
"target": {
"tagged_key": {
"key": "bcea4e71273b467ef90b55798e71d5daff676de3719f69248b209072d98cdb39",
"view_tag": "49"
}
}
}
],
"extra": [ 1, 16, 187, 241, 184, 5, 203, 120, 61, 84, 18, 59, 172, 127, 154, 154, 66, 168, 221, 221, 194, 135, 56, 180, 14, 189, 22, 144, 88, 153, 189, 244, 203, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}