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: de897af071397fa35f83aae79ddf196fa8d3f2df26407a4cd4989ec7c7d830eb
Tx prefix hash: e5893d6f83dcd381af78cd1d2a4e7930c094f770b219cc45e03ac3c261b40713
Tx public key: 2d79d19f33ec3b716b0e6f12ce8a8c06b74476acc138e2eb284b396ad53c2343
| Timestamp: 1779999652 | Timestamp [UTC]: 2026-05-28 20:20:52 | Age [y:d:h:m:s]: 00:011:08:12:10 |
| Block: 4051 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3958 | RingCT/type: yes/0 |
| Extra: 012d79d19f33ec3b716b0e6f12ce8a8c06b74476acc138e2eb284b396ad53c234302090000000426697be300 | ||
1 output(s) for total of 34.913627994702 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb021860b8afd803e428f6af75d90a17d3bdf7bd12bc1ea6bfde0aea0d1a01c4 | 34.913627994702 | 5019 of 0 | <34> |
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": 4111,
"vin": [ {
"gen": {
"height": 4051
}
}
],
"vout": [ {
"amount": 34913627994702,
"target": {
"tagged_key": {
"key": "eb021860b8afd803e428f6af75d90a17d3bdf7bd12bc1ea6bfde0aea0d1a01c4",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 45, 121, 209, 159, 51, 236, 59, 113, 107, 14, 111, 18, 206, 138, 140, 6, 183, 68, 118, 172, 193, 56, 226, 235, 40, 75, 57, 106, 213, 60, 35, 67, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}