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: 4ddd1e0b5419100c044068f0306f07807d7e10cedafc6a6ba27aa651ee5a8fb9
Tx prefix hash: e41873693faa867d6ecefe8595820ff0ec85d5895700e2e88c45dde8e8340b0e
Tx public key: e3d771051b8487b26292be7b029035d9241a7d3761892709494c318379b4f679
| Timestamp: 1780775031 | Timestamp [UTC]: 2026-06-06 19:43:51 | Age [y:d:h:m:s]: 00:002:05:52:06 |
| Block: 6710 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1176 | RingCT/type: yes/0 |
| Extra: 01e3d771051b8487b26292be7b029035d9241a7d3761892709494c318379b4f679020900000001e49593ff00 | ||
1 output(s) for total of 34.737006731781 HMNY
| stealth address | amount | amount idx | tag |
| 00: 559f4df75fd721d7300b463f5511bf25833b26ade1effd8a429e154bf362f7ca | 34.737006731781 | 8276 of 0 | <2a> |
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": 6770,
"vin": [ {
"gen": {
"height": 6710
}
}
],
"vout": [ {
"amount": 34737006731781,
"target": {
"tagged_key": {
"key": "559f4df75fd721d7300b463f5511bf25833b26ade1effd8a429e154bf362f7ca",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 227, 215, 113, 5, 27, 132, 135, 178, 98, 146, 190, 123, 2, 144, 53, 217, 36, 26, 125, 55, 97, 137, 39, 9, 73, 76, 49, 131, 121, 180, 246, 121, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}