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: ee2e5351c286c17763bda308553bf086784e2e2563c5db1aeeb61e4aa9b98a3e
Tx prefix hash: a5a321d91228e4f245b13f8efea786678cb35c515a66041fc883a03b2180309f
Tx public key: c4a2f73e888b4873f1b6f1103d20703ff2315e103f0bc1a395de3b7c643127aa
| Timestamp: 1779782404 | Timestamp [UTC]: 2026-05-26 08:00:04 | Age [y:d:h:m:s]: 00:013:18:40:32 |
| Block: 2125 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5771 | RingCT/type: yes/0 |
| Extra: 01c4a2f73e888b4873f1b6f1103d20703ff2315e103f0bc1a395de3b7c643127aa02090000000226697be300 | ||
1 output(s) for total of 35.042121064982 HMNY
| stealth address | amount | amount idx | tag |
| 00: b6ecc284a58c6debadf0b052a8e95fba4478a209c456181242816039057b5d60 | 35.042121064982 | 2449 of 0 | <1e> |
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": 2185,
"vin": [ {
"gen": {
"height": 2125
}
}
],
"vout": [ {
"amount": 35042121064982,
"target": {
"tagged_key": {
"key": "b6ecc284a58c6debadf0b052a8e95fba4478a209c456181242816039057b5d60",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 196, 162, 247, 62, 136, 139, 72, 115, 241, 182, 241, 16, 61, 32, 112, 63, 242, 49, 94, 16, 63, 11, 193, 163, 149, 222, 59, 124, 100, 49, 39, 170, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}