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: c5babbb54a07df2f6c70075b601ef9f0d9b2821a51452fce270bea4f9f1f3b53
Tx prefix hash: 84edd5aaa3691d86eb7101891d95417078b990a5391a9219b670eabc50129af4
Tx public key: 78b56a954ccee1da0b4a1dc46aa9e7ea3542a565fec5922cd38f07b3465493d0
| Timestamp: 1779642984 | Timestamp [UTC]: 2026-05-24 17:16:24 | Age [y:d:h:m:s]: 00:015:08:19:33 |
| Block: 1399 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6487 | RingCT/type: yes/0 |
| Extra: 0178b56a954ccee1da0b4a1dc46aa9e7ea3542a565fec5922cd38f07b3465493d0020900000002ba6d17be00 | ||
1 output(s) for total of 35.090678778593 HMNY
| stealth address | amount | amount idx | tag |
| 00: 735e60e7237f5efe5b68d75cd55e7c07418bf30df0e7a72abe19cbe8d49f318f | 35.090678778593 | 1551 of 0 | <74> |
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": 1459,
"vin": [ {
"gen": {
"height": 1399
}
}
],
"vout": [ {
"amount": 35090678778593,
"target": {
"tagged_key": {
"key": "735e60e7237f5efe5b68d75cd55e7c07418bf30df0e7a72abe19cbe8d49f318f",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 120, 181, 106, 149, 76, 206, 225, 218, 11, 74, 29, 196, 106, 169, 231, 234, 53, 66, 165, 101, 254, 197, 146, 44, 211, 143, 7, 179, 70, 84, 147, 208, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}