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: 48d71cdc09fc95f86a61acfc4fc371fb652797b20470cc7b6da1003b77e2a577
Tx prefix hash: b0fe55974833c7b50de7a24c4c6ef9b34d764201024667cee5ee0c654b560d96
Tx public key: 970e50735bb7e607a3acc6c02a7ea2602a14b30887cb4c8761d06b0bd23b4178
| Timestamp: 1779477062 | Timestamp [UTC]: 2026-05-22 19:11:02 | Age [y:d:h:m:s]: 00:017:21:58:01 |
| Block: 623 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8111 | RingCT/type: yes/0 |
| Extra: 01970e50735bb7e607a3acc6c02a7ea2602a14b30887cb4c8761d06b0bd23b417802090000000593369e7d00 | ||
1 output(s) for total of 35.142655086563 HMNY
| stealth address | amount | amount idx | tag |
| 00: ebc5021f315e0fae2d7ea4ad202ea5a09ffc2ffc00b83af280b5b05c5615737a | 35.142655086563 | 648 of 0 | <c2> |
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": 683,
"vin": [ {
"gen": {
"height": 623
}
}
],
"vout": [ {
"amount": 35142655086563,
"target": {
"tagged_key": {
"key": "ebc5021f315e0fae2d7ea4ad202ea5a09ffc2ffc00b83af280b5b05c5615737a",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 151, 14, 80, 115, 91, 183, 230, 7, 163, 172, 198, 192, 42, 126, 162, 96, 42, 20, 179, 8, 135, 203, 76, 135, 97, 208, 107, 11, 210, 59, 65, 120, 2, 9, 0, 0, 0, 5, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}