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: 12fbb0d6c0116ae0a21933cad25bac213c70d510d4be6208dad3590948b13895
Tx prefix hash: d0a1cda049cd31f6d1e67b71bd6f9b0fc99938885e0f65b0da35b622892eae02
Tx public key: b09f5a1aeeae76f6323b2389fcabd7f6e80216d8d48a83f5a1be3d2f3ed8ef30
| Timestamp: 1779894266 | Timestamp [UTC]: 2026-05-27 15:04:26 | Age [y:d:h:m:s]: 00:012:09:42:21 |
| Block: 3086 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4800 | RingCT/type: yes/0 |
| Extra: 01b09f5a1aeeae76f6323b2389fcabd7f6e80216d8d48a83f5a1be3d2f3ed8ef3002090000000226697be300 | ||
1 output(s) for total of 34.977948956691 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9d4937ab06d4e599fd36698f677d67df454815d964aaae1737747ef12f36a792 | 34.977948956691 | 3678 of 0 | <c2> |
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": 3146,
"vin": [ {
"gen": {
"height": 3086
}
}
],
"vout": [ {
"amount": 34977948956691,
"target": {
"tagged_key": {
"key": "9d4937ab06d4e599fd36698f677d67df454815d964aaae1737747ef12f36a792",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 176, 159, 90, 26, 238, 174, 118, 246, 50, 59, 35, 137, 252, 171, 215, 246, 232, 2, 22, 216, 212, 138, 131, 245, 161, 190, 61, 47, 62, 216, 239, 48, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}