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: 4823c483ab71821d826847ab04d79b57ddde750a6abfca5d3948dcb4fc1be149
Tx prefix hash: 537c86a997f35096b2418224d354c2956a9315ee1c401ccde1782a42e936fb6b
Tx public key: 2ec37fa609439afef646b5fae40d45b9a286c760ede356b053bf141cb215bd6d
| Timestamp: 1779766926 | Timestamp [UTC]: 2026-05-26 03:42:06 | Age [y:d:h:m:s]: 00:013:21:53:51 |
| Block: 1977 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5909 | RingCT/type: yes/0 |
| Extra: 012ec37fa609439afef646b5fae40d45b9a286c760ede356b053bf141cb215bd6d02090000000126697be300 | ||
1 output(s) for total of 35.052014426910 HMNY
| stealth address | amount | amount idx | tag |
| 00: c17a5a8143c2db525079459fcb3a2f3941488d575cd6ab0e5b29b8ef6bd505a7 | 35.052014426910 | 2249 of 0 | <a0> |
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": 2037,
"vin": [ {
"gen": {
"height": 1977
}
}
],
"vout": [ {
"amount": 35052014426910,
"target": {
"tagged_key": {
"key": "c17a5a8143c2db525079459fcb3a2f3941488d575cd6ab0e5b29b8ef6bd505a7",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 46, 195, 127, 166, 9, 67, 154, 254, 246, 70, 181, 250, 228, 13, 69, 185, 162, 134, 199, 96, 237, 227, 86, 176, 83, 191, 20, 28, 178, 21, 189, 109, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}