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: 25bb66d24916a3b325db78829e4f2512b3f6628ee3840aacde1f440c3b7d721e
Tx prefix hash: b7c4eb818c720ffe53d32b7478a96b1337c7664ae640057f28d3f370ff1f5dd1
Tx public key: ca4c54e2ebb57f706457725eb3a6ca93a3dbb35e8c2b3e8c17964f26eb1dd3c9
| Timestamp: 1780701543 | Timestamp [UTC]: 2026-06-05 23:19:03 | Age [y:d:h:m:s]: 00:003:02:16:54 |
| Block: 6060 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1826 | RingCT/type: yes/0 |
| Extra: 01ca4c54e2ebb57f706457725eb3a6ca93a3dbb35e8c2b3e8c17964f26eb1dd3c9020900000001e49593ff00 | ||
1 output(s) for total of 34.780099608622 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b7ddbaf8e4aa2dd40731bf92f70969eee3822a451abd3e05e2b11bb2a62b6bc | 34.780099608622 | 7529 of 0 | <21> |
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": 6120,
"vin": [ {
"gen": {
"height": 6060
}
}
],
"vout": [ {
"amount": 34780099608622,
"target": {
"tagged_key": {
"key": "2b7ddbaf8e4aa2dd40731bf92f70969eee3822a451abd3e05e2b11bb2a62b6bc",
"view_tag": "21"
}
}
}
],
"extra": [ 1, 202, 76, 84, 226, 235, 181, 127, 112, 100, 87, 114, 94, 179, 166, 202, 147, 163, 219, 179, 94, 140, 43, 62, 140, 23, 150, 79, 38, 235, 29, 211, 201, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}