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: c03a5b50eab15a8f128f7524428a5a9b266ed94b2fabc4d9cbe76c0f28c29815
Tx prefix hash: 2f89f614003fa6e3ec0d7775a8317ad7f11aa0eaed6ac095ebaa20f95fccc6c9
Tx public key: 42992c81e19cd3fd3cfa31f39ed3d0b9bc7f4375db529864dbb8939ade44739a
| Timestamp: 1780688032 | Timestamp [UTC]: 2026-06-05 19:33:52 | Age [y:d:h:m:s]: 00:003:08:17:06 |
| Block: 5507 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2459 | RingCT/type: yes/0 |
| Extra: 0142992c81e19cd3fd3cfa31f39ed3d0b9bc7f4375db529864dbb8939ade44739a020900000001e49593ff00 | ||
1 output(s) for total of 34.816803787160 HMNY
| stealth address | amount | amount idx | tag |
| 00: ae6e24afdc28c6a791f9b423d533d178e1b8894cb631beb24df5ab339e4632b0 | 34.816803787160 | 6948 of 0 | <96> |
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": 5567,
"vin": [ {
"gen": {
"height": 5507
}
}
],
"vout": [ {
"amount": 34816803787160,
"target": {
"tagged_key": {
"key": "ae6e24afdc28c6a791f9b423d533d178e1b8894cb631beb24df5ab339e4632b0",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 66, 153, 44, 129, 225, 156, 211, 253, 60, 250, 49, 243, 158, 211, 208, 185, 188, 127, 67, 117, 219, 82, 152, 100, 219, 184, 147, 154, 222, 68, 115, 154, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}