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: 2d403c2e73b8aedbfb99704ec8fa34a66fa101d2c97567af0d7ac6550f6d7cb3
Tx prefix hash: d6293ee255d556cd35e22fc4ec8f90865743325a8ec557e432c43eee0ce08272
Tx public key: 4d077bbf9e1d652d0110c4c2692b31742f495d97e4b4f4512e2310d04315d91c
| Timestamp: 1779447812 | Timestamp [UTC]: 2026-05-22 11:03:32 | Age [y:d:h:m:s]: 00:017:15:37:04 |
| Block: 289 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7605 | RingCT/type: yes/0 |
| Extra: 014d077bbf9e1d652d0110c4c2692b31742f495d97e4b4f4512e2310d04315d91c0209000000014438f87f00 | ||
1 output(s) for total of 35.165050025135 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9d1a5ebc764e51db6704a68955dfa1e25966e331e6640ab91b9985e8b091721 | 35.165050025135 | 285 of 0 | <e4> |
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": 349,
"vin": [ {
"gen": {
"height": 289
}
}
],
"vout": [ {
"amount": 35165050025135,
"target": {
"tagged_key": {
"key": "d9d1a5ebc764e51db6704a68955dfa1e25966e331e6640ab91b9985e8b091721",
"view_tag": "e4"
}
}
}
],
"extra": [ 1, 77, 7, 123, 191, 158, 29, 101, 45, 1, 16, 196, 194, 105, 43, 49, 116, 47, 73, 93, 151, 228, 180, 244, 81, 46, 35, 16, 208, 67, 21, 217, 28, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}