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: 6a25126b3510ff707c0da9617d24552bc0779ac1effbc6d4c0cb23ccdcdac247
Tx prefix hash: d7e538977a3b1008ea009cb3a5bcb3abf1d9f0824ddbb69a96ecff66f4f93a7d
Tx public key: 95958ba9a63d096b44df9f01365dea8bddecdb4ee594a83c836dbd8204d309c0
| Timestamp: 1780029381 | Timestamp [UTC]: 2026-05-29 04:36:21 | Age [y:d:h:m:s]: 00:010:22:04:15 |
| Block: 4190 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3706 | RingCT/type: yes/0 |
| Extra: 0195958ba9a63d096b44df9f01365dea8bddecdb4ee594a83c836dbd8204d309c002090000000226697be300 | ||
1 output(s) for total of 34.904372860771 HMNY
| stealth address | amount | amount idx | tag |
| 00: 94f5c160a22563dc768325e363231f5e265a9b7effc963f5cfbd9286d1aa6b13 | 34.904372860771 | 5223 of 0 | <78> |
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": 4250,
"vin": [ {
"gen": {
"height": 4190
}
}
],
"vout": [ {
"amount": 34904372860771,
"target": {
"tagged_key": {
"key": "94f5c160a22563dc768325e363231f5e265a9b7effc963f5cfbd9286d1aa6b13",
"view_tag": "78"
}
}
}
],
"extra": [ 1, 149, 149, 139, 169, 166, 61, 9, 107, 68, 223, 159, 1, 54, 93, 234, 139, 221, 236, 219, 78, 229, 148, 168, 60, 131, 109, 189, 130, 4, 211, 9, 192, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}