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: f045727b8b02c3c3b9d8426918321937b23b4fec983c6dc84af84cbbfb4afa55
Tx prefix hash: f5669f076e59be8aca5538e7fdf485fdd4c26d93f8248febbdd8320758dde62d
Tx public key: d8ada9c0a33c98b3e622206656f7b939c7447871410ce7c62b76f1bb0fb6de4f
| Timestamp: 1780861186 | Timestamp [UTC]: 2026-06-07 19:39:46 | Age [y:d:h:m:s]: 00:001:03:39:07 |
| Block: 7619 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 267 | RingCT/type: yes/0 |
| Extra: 01d8ada9c0a33c98b3e622206656f7b939c7447871410ce7c62b76f1bb0fb6de4f020900000002e49593ff00 | ||
1 output(s) for total of 34.683460129571 HMNY
| stealth address | amount | amount idx | tag |
| 00: a3eb5b3a88ac77c36625546f3061a813d990e8c15ca06be5026d7b86601bea52 | 34.683460129571 | 9415 of 0 | <11> |
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": 7679,
"vin": [ {
"gen": {
"height": 7619
}
}
],
"vout": [ {
"amount": 34683460129571,
"target": {
"tagged_key": {
"key": "a3eb5b3a88ac77c36625546f3061a813d990e8c15ca06be5026d7b86601bea52",
"view_tag": "11"
}
}
}
],
"extra": [ 1, 216, 173, 169, 192, 163, 60, 152, 179, 230, 34, 32, 102, 86, 247, 185, 57, 199, 68, 120, 113, 65, 12, 231, 198, 43, 118, 241, 187, 15, 182, 222, 79, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}