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: 97521881c50204ff6ee8b97799c2ac1a8ef41a2405e3b35f62ea447975373926
Tx prefix hash: 6eae92bbfc13cf3bdf7a0ebbb30c8419458c5189ee7634cca0d2b4d00cfd49a1
Tx public key: 0b2afd49d76f3a8e8d851a9c56da50b0072891fadfa844f164b7ed753ac91696
| Timestamp: 1780110530 | Timestamp [UTC]: 2026-05-30 03:08:50 | Age [y:d:h:m:s]: 00:009:23:40:58 |
| Block: 4853 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3047 | RingCT/type: yes/0 |
| Extra: 010b2afd49d76f3a8e8d851a9c56da50b0072891fadfa844f164b7ed753ac9169602090000000426697be300 | ||
1 output(s) for total of 34.862877617898 HMNY
| stealth address | amount | amount idx | tag |
| 00: af2a378cc42bd55f6f0eac9835b59d4b40708be2447a846d3baa4aef1bb368c8 | 34.862877617898 | 6125 of 0 | <ee> |
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": 4913,
"vin": [ {
"gen": {
"height": 4853
}
}
],
"vout": [ {
"amount": 34862877617898,
"target": {
"tagged_key": {
"key": "af2a378cc42bd55f6f0eac9835b59d4b40708be2447a846d3baa4aef1bb368c8",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 11, 42, 253, 73, 215, 111, 58, 142, 141, 133, 26, 156, 86, 218, 80, 176, 7, 40, 145, 250, 223, 168, 68, 241, 100, 183, 237, 117, 58, 201, 22, 150, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}