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: d0a3b2e2b1a82540294a8b869450de7a14026c081a0dd447d9cce2c2d44c2623
Tx prefix hash: 4a39613512110912b7ab5a0c77c385d7de8da4d178e7a69922641d2689f9db9f
Tx public key: e2d1617de50f6debc5e42c96aa451e5dfa3371f8655be12cfe35d10fdcda224f
| Timestamp: 1780689808 | Timestamp [UTC]: 2026-06-05 20:03:28 | Age [y:d:h:m:s]: 00:003:03:15:25 |
| Block: 5623 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2263 | RingCT/type: yes/0 |
| Extra: 01e2d1617de50f6debc5e42c96aa451e5dfa3371f8655be12cfe35d10fdcda224f020900000001e49593ff00 | ||
1 output(s) for total of 34.809101329099 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84099aac713f127f546593b0aba579ad32fdb596e50aa2d7572a8b503eadce05 | 34.809101329099 | 7070 of 0 | <5e> |
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": 5683,
"vin": [ {
"gen": {
"height": 5623
}
}
],
"vout": [ {
"amount": 34809101329099,
"target": {
"tagged_key": {
"key": "84099aac713f127f546593b0aba579ad32fdb596e50aa2d7572a8b503eadce05",
"view_tag": "5e"
}
}
}
],
"extra": [ 1, 226, 209, 97, 125, 229, 15, 109, 235, 197, 228, 44, 150, 170, 69, 30, 93, 250, 51, 113, 248, 101, 91, 225, 44, 254, 53, 209, 15, 220, 218, 34, 79, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}