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: 52298d2020044d4a55ac0dc03786b5707f9196d887be4ed5f53cd470056bdfec
Tx prefix hash: 4f99fce0da1a84f2f4ae0290273fdd79c395384f32f1d06c10d643a063053250
Tx public key: 80a123e74990bfa4a41ffdd10d401c6a741fda5d2664c1628f67a5d2a4e9d4a4
| Timestamp: 1779955288 | Timestamp [UTC]: 2026-05-28 08:01:28 | Age [y:d:h:m:s]: 00:011:17:34:29 |
| Block: 3683 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4203 | RingCT/type: yes/0 |
| Extra: 0180a123e74990bfa4a41ffdd10d401c6a741fda5d2664c1628f67a5d2a4e9d4a402090000000526697be300 | ||
1 output(s) for total of 34.938142646053 HMNY
| stealth address | amount | amount idx | tag |
| 00: 59cb424304fb9b26d48c24e03bdae604eb6dd2342ead65d4ecaa4a43a60fb292 | 34.938142646053 | 4453 of 0 | <7b> |
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": 3743,
"vin": [ {
"gen": {
"height": 3683
}
}
],
"vout": [ {
"amount": 34938142646053,
"target": {
"tagged_key": {
"key": "59cb424304fb9b26d48c24e03bdae604eb6dd2342ead65d4ecaa4a43a60fb292",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 128, 161, 35, 231, 73, 144, 191, 164, 164, 31, 253, 209, 13, 64, 28, 106, 116, 31, 218, 93, 38, 100, 193, 98, 143, 103, 165, 210, 164, 233, 212, 164, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}