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: 4156a4aa52d9a83a1ed6007131fd9183477f84e2e7c280127c98dab367900c8f
Tx prefix hash: dc1c1ae8eb4fcfdf493a3bebdf37cd4aa8f8183e6c44ecab899b192ca52ccb2e
Tx public key: ac4fb4e9fcda037b181117c7f9eecb33f562baac6ce35ba7fb86c9bd05affcc6
| Timestamp: 1780393816 | Timestamp [UTC]: 2026-06-02 09:50:16 | Age [y:d:h:m:s]: 00:006:15:45:41 |
| Block: 5232 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2654 | RingCT/type: yes/0 |
| Extra: 01ac4fb4e9fcda037b181117c7f9eecb33f562baac6ce35ba7fb86c9bd05affcc602090000000326697be300 | ||
1 output(s) for total of 34.835070735213 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74496b8488004b16cfe2fa2261d669f9e7b88d49e8ceefad3a1b3b6736e13c24 | 34.835070735213 | 6623 of 0 | <ae> |
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": 5292,
"vin": [ {
"gen": {
"height": 5232
}
}
],
"vout": [ {
"amount": 34835070735213,
"target": {
"tagged_key": {
"key": "74496b8488004b16cfe2fa2261d669f9e7b88d49e8ceefad3a1b3b6736e13c24",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 172, 79, 180, 233, 252, 218, 3, 123, 24, 17, 23, 199, 249, 238, 203, 51, 245, 98, 186, 172, 108, 227, 91, 167, 251, 134, 201, 189, 5, 175, 252, 198, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}