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: dd1c621d86dfe518d87923025d0efd0e2b56bc9934f9c245ef34072eacae5ddf
Tx prefix hash: 0b4554055ac6a6668c6d917e26f073bc30b13b02319f907a181e5f066633da7d
Tx public key: 050edea1023584a883ae4e974392110d192c03db131f25bcab40c8407b291542
| Timestamp: 1779478093 | Timestamp [UTC]: 2026-05-22 19:28:13 | Age [y:d:h:m:s]: 00:017:07:12:23 |
| Block: 628 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7268 | RingCT/type: yes/0 |
| Extra: 01050edea1023584a883ae4e974392110d192c03db131f25bcab40c8407b29154202090000000293369e7d00 | ||
1 output(s) for total of 35.148003141366 HMNY
| stealth address | amount | amount idx | tag |
| 00: 69e35d496919f3933736eb6faf33d4e8aec3d8c418409f5d6e121bbce1b2be77 | 35.148003141366 | 656 of 0 | <bb> |
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": 688,
"vin": [ {
"gen": {
"height": 628
}
}
],
"vout": [ {
"amount": 35148003141366,
"target": {
"tagged_key": {
"key": "69e35d496919f3933736eb6faf33d4e8aec3d8c418409f5d6e121bbce1b2be77",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 5, 14, 222, 161, 2, 53, 132, 168, 131, 174, 78, 151, 67, 146, 17, 13, 25, 44, 3, 219, 19, 31, 37, 188, 171, 64, 200, 64, 123, 41, 21, 66, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}