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: 53cb4f106137e88216c6b44656b7c5367eb14aa5e71c4c0f17afac7eacb643e9
Tx prefix hash: 0edbe4c2fcb0ec0940583956905dcfb6f92753e7ca039f75ed99eb26a97bd889
Tx public key: 0b70756d4236b8d69902698355568fcb0788b05a38483d9c183ce2677428b901
| Timestamp: 1779806675 | Timestamp [UTC]: 2026-05-26 14:44:35 | Age [y:d:h:m:s]: 00:013:10:02:12 |
| Block: 2357 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5529 | RingCT/type: yes/0 |
| Extra: 010b70756d4236b8d69902698355568fcb0788b05a38483d9c183ce2677428b90102090000000226697be300 | ||
1 output(s) for total of 35.026618170828 HMNY
| stealth address | amount | amount idx | tag |
| 00: 15eae78f1afb95428bde2a0c389fb7a7634f002e232fc3f88a4ca2b0064291a2 | 35.026618170828 | 2761 of 0 | <9a> |
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": 2417,
"vin": [ {
"gen": {
"height": 2357
}
}
],
"vout": [ {
"amount": 35026618170828,
"target": {
"tagged_key": {
"key": "15eae78f1afb95428bde2a0c389fb7a7634f002e232fc3f88a4ca2b0064291a2",
"view_tag": "9a"
}
}
}
],
"extra": [ 1, 11, 112, 117, 109, 66, 54, 184, 214, 153, 2, 105, 131, 85, 86, 143, 203, 7, 136, 176, 90, 56, 72, 61, 156, 24, 60, 226, 103, 116, 40, 185, 1, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}