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: b311116c9cdec4fcb4869ab8b33d097b9d832e2750b5f95542ca9a3c13c15e3a
Tx prefix hash: 38b20221fac88dc020049d53a59097cd26e19e6dcd66e6d718be81c90bfdfae2
Tx public key: 95fcc6a5878edf827e5cc2094bdbb68e7c9e0bb769e2a0ae14a7e619d9dd0ad7
| Timestamp: 1779481551 | Timestamp [UTC]: 2026-05-22 20:25:51 | Age [y:d:h:m:s]: 00:017:06:23:57 |
| Block: 653 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7267 | RingCT/type: yes/0 |
| Extra: 0195fcc6a5878edf827e5cc2094bdbb68e7c9e0bb769e2a0ae14a7e619d9dd0ad702090000000693369e7d00 | ||
1 output(s) for total of 35.143243463322 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a8eb5a3ccdd8fed67b763e75b1a9b1b1a9a34401389274551f53d16e5de261e | 35.143243463322 | 698 of 0 | <35> |
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": 713,
"vin": [ {
"gen": {
"height": 653
}
}
],
"vout": [ {
"amount": 35143243463322,
"target": {
"tagged_key": {
"key": "5a8eb5a3ccdd8fed67b763e75b1a9b1b1a9a34401389274551f53d16e5de261e",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 149, 252, 198, 165, 135, 142, 223, 130, 126, 92, 194, 9, 75, 219, 182, 142, 124, 158, 11, 183, 105, 226, 160, 174, 20, 167, 230, 25, 217, 221, 10, 215, 2, 9, 0, 0, 0, 6, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}