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: c78ab5b1943dccccf831db5588920d61a2fd2253b9fb330ccacaeee3f0a61fcd
Tx prefix hash: a8f6415452b8637dcad53bbacceb304cee125aea9315cf0efcd20f8f64e9147b
Tx public key: 30d3e0765e2aed43990eaaee8e14ef501f2a9bc40631b0a35d34a9272ad6878e
| Timestamp: 1779716877 | Timestamp [UTC]: 2026-05-25 13:47:57 | Age [y:d:h:m:s]: 00:014:11:48:00 |
| Block: 1664 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6222 | RingCT/type: yes/0 |
| Extra: 0130d3e0765e2aed43990eaaee8e14ef501f2a9bc40631b0a35d34a9272ad6878e020900000001ba6d17be00 | ||
1 output(s) for total of 35.072946751443 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4bc3ede3073391d2b3dc6d416ea992819342cb510398961cadcf0936022d3872 | 35.072946751443 | 1828 of 0 | <ce> |
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": 1724,
"vin": [ {
"gen": {
"height": 1664
}
}
],
"vout": [ {
"amount": 35072946751443,
"target": {
"tagged_key": {
"key": "4bc3ede3073391d2b3dc6d416ea992819342cb510398961cadcf0936022d3872",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 48, 211, 224, 118, 94, 42, 237, 67, 153, 14, 170, 238, 142, 20, 239, 80, 31, 42, 155, 196, 6, 49, 176, 163, 93, 52, 169, 39, 42, 214, 135, 142, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}