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: 5b4ff1e4a87062ead38e855295b338e7497aa29870290aca26e2547bccc443b3
Tx prefix hash: 45e6578a6b3f0d6e48f0097c8fa24facd6074a7d37283b870bd4a8319750421b
Tx public key: 7e7664fd1513e3336e49a171c89a9bcf1bbc5e621e919cb56e8cc880cb1515ce
| Timestamp: 1780988692 | Timestamp [UTC]: 2026-06-09 07:04:52 | Age [y:d:h:m:s]: 00:000:08:54:52 |
| Block: 8188 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 503 | RingCT/type: yes/0 |
| Extra: 017e7664fd1513e3336e49a171c89a9bcf1bbc5e621e919cb56e8cc880cb1515ce020900000001e49593ff00 | ||
1 output(s) for total of 34.639218787752 HMNY
| stealth address | amount | amount idx | tag |
| 00: 26c1fa08bb233d9952092b07dbb8d5799dfd228155b6140efa1f515ba9eff451 | 34.639218787752 | 10138 of 0 | <d2> |
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": 8248,
"vin": [ {
"gen": {
"height": 8188
}
}
],
"vout": [ {
"amount": 34639218787752,
"target": {
"tagged_key": {
"key": "26c1fa08bb233d9952092b07dbb8d5799dfd228155b6140efa1f515ba9eff451",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 126, 118, 100, 253, 21, 19, 227, 51, 110, 73, 161, 113, 200, 154, 155, 207, 27, 188, 94, 98, 30, 145, 156, 181, 110, 140, 200, 128, 203, 21, 21, 206, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}