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: d18261749148b1101970d350a1d6ac5be575889d7b545aec490b65470a8195ed
Tx prefix hash: 45baeca71c2b865ea0fbb91a0796348605a03ceb03688a0b6ca73f883317524e
Tx public key: 806f8363e7d4d0c2d68c5c2d3bad793be0b06f66e6ecc9939cb3d1c017330347
| Timestamp: 1780727535 | Timestamp [UTC]: 2026-06-06 06:32:15 | Age [y:d:h:m:s]: 00:002:20:17:33 |
| Block: 6287 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1613 | RingCT/type: yes/0 |
| Extra: 01806f8363e7d4d0c2d68c5c2d3bad793be0b06f66e6ecc9939cb3d1c017330347020900000001e49593ff00 | ||
1 output(s) for total of 34.765044178736 HMNY
| stealth address | amount | amount idx | tag |
| 00: 896a130eee90809ff65f4d05ef94a18ce07bb43ad6c0ac888172485bcdc5d226 | 34.765044178736 | 7770 of 0 | <16> |
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": 6347,
"vin": [ {
"gen": {
"height": 6287
}
}
],
"vout": [ {
"amount": 34765044178736,
"target": {
"tagged_key": {
"key": "896a130eee90809ff65f4d05ef94a18ce07bb43ad6c0ac888172485bcdc5d226",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 128, 111, 131, 99, 231, 212, 208, 194, 214, 140, 92, 45, 59, 173, 121, 59, 224, 176, 111, 102, 230, 236, 201, 147, 156, 179, 209, 192, 23, 51, 3, 71, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}