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: 7541dd8cd6372fa03443a07186dc7c7428a885081c4e0b4cd3a6655ad5d9a490
Tx prefix hash: a6bef5424921f167754cf14ae15a98ebab4e3537b2f382d0ebacdf6beee69a65
Tx public key: 36b34d64a94e2416598c85aad75443e51406e7a84560424fe79397c3b68bbdb5
| Timestamp: 1779453220 | Timestamp [UTC]: 2026-05-22 12:33:40 | Age [y:d:h:m:s]: 00:017:13:02:17 |
| Block: 349 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7537 | RingCT/type: yes/0 |
| Extra: 0136b34d64a94e2416598c85aad75443e51406e7a84560424fe79397c3b68bbdb502090000000293369e7d00 | ||
1 output(s) for total of 35.161025930957 HMNY
| stealth address | amount | amount idx | tag |
| 00: 61a9061444edf0e739e4de8b0ff4d9e548bf5849c17e8f1ce678b16e8717ac9c | 35.161025930957 | 345 of 0 | <81> |
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": 409,
"vin": [ {
"gen": {
"height": 349
}
}
],
"vout": [ {
"amount": 35161025930957,
"target": {
"tagged_key": {
"key": "61a9061444edf0e739e4de8b0ff4d9e548bf5849c17e8f1ce678b16e8717ac9c",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 54, 179, 77, 100, 169, 78, 36, 22, 89, 140, 133, 170, 215, 84, 67, 229, 20, 6, 231, 168, 69, 96, 66, 79, 231, 147, 151, 195, 182, 139, 189, 181, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}