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: d117979546e194d1cc6ff43424748bfd5caa5036d87e95e80ad116c367f8fe4e
Tx prefix hash: 70d86d1aaac2fb29ff6c9639878e03543e4b8e2e98826e6b8143faf031d1291a
Tx public key: 0b9cb02224527e9ef7d9364f8cefc54ef3584efd5bebb778e1a1b72b9bf139fc
| Timestamp: 1780974570 | Timestamp [UTC]: 2026-06-09 03:09:30 | Age [y:d:h:m:s]: 00:000:08:17:18 |
| Block: 7920 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 590 | RingCT/type: yes/0 |
| Extra: 010b9cb02224527e9ef7d9364f8cefc54ef3584efd5bebb778e1a1b72b9bf139fc020900000004e49593ff00 | ||
1 output(s) for total of 34.666756640779 HMNY
| stealth address | amount | amount idx | tag |
| 00: c015c03cb22b23781dfa891d96301658999a15db45fed4e2ee8e857ae7e79960 | 34.666756640779 | 9820 of 0 | <f0> |
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": 7980,
"vin": [ {
"gen": {
"height": 7920
}
}
],
"vout": [ {
"amount": 34666756640779,
"target": {
"tagged_key": {
"key": "c015c03cb22b23781dfa891d96301658999a15db45fed4e2ee8e857ae7e79960",
"view_tag": "f0"
}
}
}
],
"extra": [ 1, 11, 156, 176, 34, 36, 82, 126, 158, 247, 217, 54, 79, 140, 239, 197, 78, 243, 88, 78, 253, 91, 235, 183, 120, 225, 161, 183, 43, 155, 241, 57, 252, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}