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: 220efdc35caef549785eceb4ef8214a03614cbbb0dec21f4986a115ffc21e52b
Tx prefix hash: efba859090580107b15ce3963f48f3b65664a87bc3901f02aa58c54718097412
Tx public key: 41d2ecb54f15ca52dde09468e21e9887e5bf13d410aef2dede46f26ee0ca937d
| Timestamp: 1779642391 | Timestamp [UTC]: 2026-05-24 17:06:31 | Age [y:d:h:m:s]: 00:023:14:58:50 |
| Block: 1385 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7360 | RingCT/type: yes/0 |
| Extra: 0141d2ecb54f15ca52dde09468e21e9887e5bf13d410aef2dede46f26ee0ca937d020900000001ba6d17be00 | ||
1 output(s) for total of 35.091615814212 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32c0b42a905460ec75dcf02882460301bd3f77dede614ae0255daaf61b55aae1 | 35.091615814212 | 1535 of 0 | <b4> |
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": 1445,
"vin": [ {
"gen": {
"height": 1385
}
}
],
"vout": [ {
"amount": 35091615814212,
"target": {
"tagged_key": {
"key": "32c0b42a905460ec75dcf02882460301bd3f77dede614ae0255daaf61b55aae1",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 65, 210, 236, 181, 79, 21, 202, 82, 221, 224, 148, 104, 226, 30, 152, 135, 229, 191, 19, 212, 16, 174, 242, 222, 222, 70, 242, 110, 224, 202, 147, 125, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}