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: 1f588536f3be55a35546bf01b9e5a9f7b644956ab9eda38451d6da0bc93eca2e
Tx prefix hash: e0e4cf2d07c553c48d3c74d4ece54cce7a8f2f0b67d3b40d44971ee65ca4dc04
Tx public key: 9efe6374f7f58043fae60c4448444f3fbb013ed3e97162b7a04dd714c2949931
| Timestamp: 1779996076 | Timestamp [UTC]: 2026-05-28 19:21:16 | Age [y:d:h:m:s]: 00:011:21:47:47 |
| Block: 4027 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4707 | RingCT/type: yes/0 |
| Extra: 019efe6374f7f58043fae60c4448444f3fbb013ed3e97162b7a04dd714c294993102090000000326697be300 | ||
1 output(s) for total of 34.915226251862 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4fab99314b95c0e6dbf2bd96f6496c1e66264e7398d9305841fabe602aea243c | 34.915226251862 | 4984 of 0 | <7a> |
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": 4087,
"vin": [ {
"gen": {
"height": 4027
}
}
],
"vout": [ {
"amount": 34915226251862,
"target": {
"tagged_key": {
"key": "4fab99314b95c0e6dbf2bd96f6496c1e66264e7398d9305841fabe602aea243c",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 158, 254, 99, 116, 247, 245, 128, 67, 250, 230, 12, 68, 72, 68, 79, 63, 187, 1, 62, 211, 233, 113, 98, 183, 160, 77, 215, 20, 194, 148, 153, 49, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}