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: d090feb01cdef781df886f74876c7b3fc45a2a7d1d77326a1b0ad90246fd09cb
Tx prefix hash: 4b32c313c6622101611d13b0bf974e8efe937fab6492c578ce81afe282571c23
Tx public key: 4122df034bb3f8c8d747c22bf568c337961886f154153aecd8bd739914d5b668
| Timestamp: 1780047316 | Timestamp [UTC]: 2026-05-29 09:35:16 | Age [y:d:h:m:s]: 00:010:15:11:31 |
| Block: 4360 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3526 | RingCT/type: yes/0 |
| Extra: 014122df034bb3f8c8d747c22bf568c337961886f154153aecd8bd739914d5b66802090000000426697be300 | ||
1 output(s) for total of 34.893056967328 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84ccbccf722e990a2cb4be3a37ec3564c2d37933e396d7cf82896dd26b89b4fa | 34.893056967328 | 5451 of 0 | <c5> |
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": 4420,
"vin": [ {
"gen": {
"height": 4360
}
}
],
"vout": [ {
"amount": 34893056967328,
"target": {
"tagged_key": {
"key": "84ccbccf722e990a2cb4be3a37ec3564c2d37933e396d7cf82896dd26b89b4fa",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 65, 34, 223, 3, 75, 179, 248, 200, 215, 71, 194, 43, 245, 104, 195, 55, 150, 24, 134, 241, 84, 21, 58, 236, 216, 189, 115, 153, 20, 213, 182, 104, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}