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: a999176dfc084d2d87487c057f44dc1e74cb2e6b221f8e16964714d24679f168
Tx prefix hash: 92bfa48da84b0424d08729bc2d65ba30f91826f5b66cc0f16538037af9bc48b2
Tx public key: 318c6b96d2b96cc6b52a768d19f962f60ee942b8a253b6e17c72065fa373f8bd
| Timestamp: 1779980500 | Timestamp [UTC]: 2026-05-28 15:01:40 | Age [y:d:h:m:s]: 00:011:08:17:13 |
| Block: 3918 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3968 | RingCT/type: yes/0 |
| Extra: 01318c6b96d2b96cc6b52a768d19f962f60ee942b8a253b6e17c72065fa373f8bd02090000000326697be300 | ||
1 output(s) for total of 34.922485923893 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9c9ada5cc3f603ae24a35b91f83b7e84b158ecf2c91aa4807d961d827d69b637 | 34.922485923893 | 4812 of 0 | <d9> |
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": 3978,
"vin": [ {
"gen": {
"height": 3918
}
}
],
"vout": [ {
"amount": 34922485923893,
"target": {
"tagged_key": {
"key": "9c9ada5cc3f603ae24a35b91f83b7e84b158ecf2c91aa4807d961d827d69b637",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 49, 140, 107, 150, 210, 185, 108, 198, 181, 42, 118, 141, 25, 249, 98, 246, 14, 233, 66, 184, 162, 83, 182, 225, 124, 114, 6, 95, 163, 115, 248, 189, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}