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: d9977adbb7c05be1239846b0cc2fe43ae258293cc4274d7ebcbdfe6af95fc75b
Tx prefix hash: 12ab05e3f9f2ebe950de56c1fd18625c1b608d0b7fa3625f59c1c5d5e01e1d72
Tx public key: 5e619bb37c7fc4ee260046c4bb080d7a15b46a93f4c4152324459293c9dce77f
| Timestamp: 1779846520 | Timestamp [UTC]: 2026-05-27 01:48:40 | Age [y:d:h:m:s]: 00:012:21:30:13 |
| Block: 2462 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5424 | RingCT/type: yes/0 |
| Extra: 015e619bb37c7fc4ee260046c4bb080d7a15b46a93f4c4152324459293c9dce77f02090000000126697be300 | ||
1 output(s) for total of 35.032589229439 HMNY
| stealth address | amount | amount idx | tag |
| 00: f72e62741cc85cc327c4376e2b61a77acf8e7fe2117e2fcf34d3e4c2f289725b | 35.032589229439 | 2894 of 0 | <6b> |
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": 2522,
"vin": [ {
"gen": {
"height": 2462
}
}
],
"vout": [ {
"amount": 35032589229439,
"target": {
"tagged_key": {
"key": "f72e62741cc85cc327c4376e2b61a77acf8e7fe2117e2fcf34d3e4c2f289725b",
"view_tag": "6b"
}
}
}
],
"extra": [ 1, 94, 97, 155, 179, 124, 127, 196, 238, 38, 0, 70, 196, 187, 8, 13, 122, 21, 180, 106, 147, 244, 196, 21, 35, 36, 69, 146, 147, 201, 220, 231, 127, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}