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: 81f39ee1533db613be5e536177b7ff39300aa71bb65ef2e15190bae1c7a3c5aa
Tx prefix hash: eef6bc97685105f19820e41da682fbc2bd1df678fd3bb034c9f1126be29aeb52
Tx public key: 1936cdfee872448ef39846caa3ccbb05e3917bd47c3d3fa16405eb09050b9c79
| Timestamp: 1779461826 | Timestamp [UTC]: 2026-05-22 14:57:06 | Age [y:d:h:m:s]: 00:017:10:38:51 |
| Block: 453 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7433 | RingCT/type: yes/0 |
| Extra: 011936cdfee872448ef39846caa3ccbb05e3917bd47c3d3fa16405eb09050b9c7902090000000293369e7d00 | ||
1 output(s) for total of 35.154051925213 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6ee715ce1e59b4e3c59cdfe36e1f86077dc80acd9e181c351afd15ec5f0c75a3 | 35.154051925213 | 457 of 0 | <a0> |
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": 513,
"vin": [ {
"gen": {
"height": 453
}
}
],
"vout": [ {
"amount": 35154051925213,
"target": {
"tagged_key": {
"key": "6ee715ce1e59b4e3c59cdfe36e1f86077dc80acd9e181c351afd15ec5f0c75a3",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 25, 54, 205, 254, 232, 114, 68, 142, 243, 152, 70, 202, 163, 204, 187, 5, 227, 145, 123, 212, 124, 61, 63, 161, 100, 5, 235, 9, 5, 11, 156, 121, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}