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: 6f8a706a3e4f7c083fb7bd8a735e9184b7fde64a06c4f5e5538a3e053137ba1e
Tx prefix hash: 49a9596a17809d75175ed7f04615228075c9e2c48b5bdb6de9f91410cded457c
Tx public key: eb3f894bce49fa6e20f66cc919b1fc2a36e7cac1cfc8ea9b880bcd552557908f
| Timestamp: 1779465939 | Timestamp [UTC]: 2026-05-22 16:05:39 | Age [y:d:h:m:s]: 00:017:08:41:08 |
| Block: 510 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7376 | RingCT/type: yes/0 |
| Extra: 01eb3f894bce49fa6e20f66cc919b1fc2a36e7cac1cfc8ea9b880bcd552557908f02090000000493369e7d00 | ||
1 output(s) for total of 35.150230220444 HMNY
| stealth address | amount | amount idx | tag |
| 00: a1056a8caf6acb2a9b2f8aa78e8021f5b1264bc0f3bcfd3d4f326099942e2041 | 35.150230220444 | 514 of 0 | <d0> |
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": 570,
"vin": [ {
"gen": {
"height": 510
}
}
],
"vout": [ {
"amount": 35150230220444,
"target": {
"tagged_key": {
"key": "a1056a8caf6acb2a9b2f8aa78e8021f5b1264bc0f3bcfd3d4f326099942e2041",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 235, 63, 137, 75, 206, 73, 250, 110, 32, 246, 108, 201, 25, 177, 252, 42, 54, 231, 202, 193, 207, 200, 234, 155, 136, 11, 205, 85, 37, 87, 144, 143, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}