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: f98117264d4b3076a82187edb1b083014237f2691cc08272f925cbba018adc64
Tx prefix hash: 5477db5da3ee8d7c6d10811784012c37b18f8a5f7b36bd0f658b0d984b8ea92e
Tx public key: 788a8ab2a987ed9e98b36cdc17d55eb8e575d9538658a8c5b1862d5a88c1cb9e
| Timestamp: 1780834605 | Timestamp [UTC]: 2026-06-07 12:16:45 | Age [y:d:h:m:s]: 00:001:08:55:22 |
| Block: 7387 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 499 | RingCT/type: yes/0 |
| Extra: 01788a8ab2a987ed9e98b36cdc17d55eb8e575d9538658a8c5b1862d5a88c1cb9e020900000002e49593ff00 | ||
1 output(s) for total of 34.692180607472 HMNY
| stealth address | amount | amount idx | tag |
| 00: 27fae70a9a60b9ab56065281bee9154d84cd9d207b0aed6343c2f96df826a799 | 34.692180607472 | 9095 of 0 | <24> |
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": 7447,
"vin": [ {
"gen": {
"height": 7387
}
}
],
"vout": [ {
"amount": 34692180607472,
"target": {
"tagged_key": {
"key": "27fae70a9a60b9ab56065281bee9154d84cd9d207b0aed6343c2f96df826a799",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 120, 138, 138, 178, 169, 135, 237, 158, 152, 179, 108, 220, 23, 213, 94, 184, 229, 117, 217, 83, 134, 88, 168, 197, 177, 134, 45, 90, 136, 193, 203, 158, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}